On Tuesday, July 9, 2013 6:17:37 AM UTC-4, James Nord (jnord) wrote:
>
> The console output appears to show the shell is running after the maven
> build (as the shell output is after the line “Waiting for Jenkins to finish
> collecting data
>
> ”)
>
>
>
> What is printed before that output
>
I am no longer receiving the (scm manipulator not settled !) error in
jenkins.log, or the "Waiting for Jenkins to finish collecting data" notice
(however I did receive this notice one more time, so perhaps it's
intermittent).
For whatever reason the m2 release plugin doesn't seem to be executing. My
project uses maven earlier in the project it's goal is compile or clean
package.
Then it executes a shell right before the m2 release stuff to echo that "it
is before m2 release" -
which is supposed to either:
-Dresume=false release:branch -DbranchName=monkey-rc2
-DupdateWorkingCopyVersions=false -DupdateBranchVersions=false
-DdryRun=false
or
-Dresume=false release:branch -DbranchName=${branchname}
-DupdateWorkingCopyVersions=false -DupdateBranchVersions=false
-DdryRun=false
Then, post m2 release, I have it IM me, which works.
But, there is no branch created, so m2 seems not to be working ... (just
seems to be skipping, as I get the IM which follows m2 release plugin in
the job).
Thanks for any more help,
Bill
P.S. If I uncheck the m2 release plugin, and in the shell where I say
"before m2 release" also add the mvn command:
cd $WORKSPACE;
/opt/jenkins/tools/Maven_2.2.1/bin/mvn release:branch
-DbranchName=${branchname} -DupdateWorkingCopyVersions=false
-DupdateBranchVersions=false -DdryRun=false
it takes the parameter, and branches the repo as specified.
>
>
> *From:* jenkins...@googlegroups.com <javascript:> [mailto:
> jenkins...@googlegroups.com <javascript:>] *On Behalf Of *spacegoose
> *Sent:* 08 July 2013 19:47
> *To:* jenkins...@googlegroups.com <javascript:>
> *Subject:* M2 Release Plugin (release:branch not working for me)
>
>
>
> I'm trying to use the M2 Release Plugin in a Jenkins 1.517 job with
> github, but it doesn't seem to be working ...
>
>
> I only want to use it to release:branch at the moment and want to give the
> branchName as a parameter, I have tried it as a parameter and hard coded
> (with and w/o -e):
>
> -Dresume=false -e release:branch -DbranchName=monkey-rc2
> -DupdateWorkingCopyVersions=false -DupdateBranchVersions=false
> -DdryRun=false
> -Dresume=false -e release:branch -DbranchName=${branchname}
> -DupdateWorkingCopyVersions=false -DupdateBranchVersions=false
> -DdryRun=false
>
>
> but it fails to execute in my job, I have an "execute shell" right before
> the m2 plugin, (e.g. echo "before m2 plugin") and that is pretty much the
> last thing that happens:
>
>
> Waiting for Jenkins to finish collecting data
>
> channel stopped
>
> [nyuCMS-test] $ /bin/sh -xe /tmp/hudson7449209946030619405.sh
>
> + echo 'before m2 plugin'
>
> before m2 plugin
>
> Finished: SUCCESS
>
>
> I do see this in the jenkins.log:
>
> (scm manipulator not settled !)
>
> I am able to execute:
>
> -Dresume=false -e release:branch -DbranchName=monkey-rc2
> -DupdateWorkingCopyVersions=false -DupdateBranchVersions=false
> -DdryRun=false
>
> on the command line, and within the project's execute shell script
> functionality, and that works, would like to use the plugin however.
>
> The Jenkins machine has push / pull access to my git repo.
>
> Thanks,
> Bill
>
> --
> 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 jenkinsci-use...@googlegroups.com <javascript:>.
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
