The git SCM plugin has a way to ignore changes to certain files, by specifying those exclusion patterns with a regular expression. It is in the "advanced" section of the plugin configuration items on the job configuration page. Your SCM plugin may have a similar setting which would allow you to ignore changes to that file as part of the process (assuming that file changes rarely for other reasons).
We used a technique like that quite successfully, though our version information was stored in a separate file dedicated to only storing the version number. On Mon, Sep 16, 2013 at 12:31 AM, Baptiste Mathus <[email protected]>wrote: > I understand you're releasing a new version for almost every commit. > Though I like the idea of continuous delivery or equivalent I'm not sure > it's conceptually correct this way. > For your issue, if you really want to stay this way, I suppose I would > just try to update the working copy at the end of the build, so that next > check doesn't see the release commit as a content commit. > > Cheers > Le 16 sept. 2013 07:25, "Manoj Kumar Bardhan" <[email protected]> > a écrit : > > Hi, >> >> I am using Maven Release Plugin for automate the build & release >> process.Its working fine but one problem I am facing. >> >> I have created a job, which is checking trunk in every 15 mins, if any >> changes found it starts the build & release process.And its working fine. >> >> But , small problem is when the release:prepare is executing , it is >> creating the tag and auto increment the trunk/pom.xml version (with >> SNAPSHOT) to next release version-SNAPSHOT. >> >> Suppose my current build version is 2.0-SNAPSHOT. After successfully >> build it create the tag with only 2.0 (without SNAPSHOT). Also it auto >> increments the pom.xml inside trunk to 2.1-SNAPSHOT. >> The problem is , when my Jenkins (crontab) checking the trunk in every 15 >> mins ,it is found a new version inside the trunk (i.e. pom.xml ). And it >> creates another build again. This process is happening again and >> again.Where as I know there is no code changes in trunk, only version has >> incremented by release:prepare command. >> >> How to avoid this. >> >> >> What mistake I did. >> Thanks in Advance. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
