I have a job that I want to run every time a commit is made to a repository. I want to avoid pulling this code down, I only want the notification build trigger. So, is there either a way to not pull down certain repositories in your SCM upon a build or a way to poll things that aren't in the SCM for a build?
相关问题
- X-I.: command not found, and failed to build certa
- Maven - Access properties on parent pom from a chi
- 2 instances of Sonar on same machine
- How to add more data to be stored in jenkins rest
- VSTS Build - Choose which unit tests run depending
相关文章
- Handling ffmpeg library interface change when upgr
- Best way to manage docker containers with supervis
- Build errors of missing packages in Visual Studio
- Jenkins Pipeline having “Multiple candidate revisi
- Forcing a TFS2010 workflow build to FAIL instead o
- Use Eclipse classpath variable to replace absolute
- Passing the Maven Debug Flag from Hudson
- Should I use xUnitPublisher or xUnitBuilder after
you could use a post commit hook to trigger your hudson job.
Since you want to avoid changing SVN, you have to write a job that gets executed every so often (may be every 5 Minutes). This jobs runs a svn command using windows bach or shell script task to get the current revision for the branch in question. You can set the status of the job to unstable if there is a change. Don't use failure because you can't distinguish than between a real failure and a repository change. I think there is a plugin that sets the job status depending on the contents of you output.
You can then use the email extension plugin to send an email every time the revision changes. You can get the revision number from the last (or better the last successful or unstable) job. You can archive a file containing the revision number on the jobs or you can set the description for the job to the revision using the description setter plugin. Have a look at Hudsons remote API for ideas on how to get the information from the previous job.
Since you run your job very often during the day. don't forget to delete old job runs. But I would keep at least two days worth of history, just in case your svn is down for 24 hours.