[JIRA] [git] (JENKINS-24879) Git Plugin env variable resolution not working in Git Publisher
tobias schaber commented on JENKINS-24879 Git Plugin env variable resolution not working in Git Publisher Hi Mark, First: Sorry for not finding the duplicate entry. Thank you for your Response, it works. Great. You helped me over! Kind regards, Tobias This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24879) Git Plugin env variable resolution not working in Git Publisher
tobias schaber resolved JENKINS-24879 as Duplicate Git Plugin env variable resolution not working in Git Publisher Change By: tobias schaber (27/Sep/14 8:25 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24879) Git Plugin envvariable resolution not working in Git Publisher
tobias schaber
created JENKINS-24879
Git Plugin envvariable resolution not working in Git Publisher
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
26/Sep/14 5:37 PM
Description:
Hi,
I'm using Git in a Jenkins process with the following URL:
http://192.168.0.17:7990/scm/sour/${REPO_NAME}.git
where REPO_NAME is given as a Parameter to the Job.
The Source Code Checkout works fine, the URL can be resolved with the variable in it.
At the end of the process I use the "Git Publisher" Post Build Action with following configuration:
Push Only If Build Succeeded (true)
Tag to push $TAG_NAME
Tag message ...
Create new tag (true)
Target remote Name: sources_repo
But now, the GIT URL from above can not be resolved as the variable REPO_NAME can not be resolved. The process Fails with the following exception:
Pushing tag testapp-1.0.0-58 to repo sources_repo
ERROR: Failed to push tag testapp-1.0.0-58 to sources_repo
hudson.plugins.git.GitException: Invalid URL http://192.168.0.17:7990/scm/sour/${REPO_NAME}.git
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:2259)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1171)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:87)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1492)
at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:298)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1040)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1770)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Build step 'Git Publisher' marked build as failure
Maybe you could have an eye on this?
Kind regards,
Tobias
Environment:
Jenkins 1.581
Git Plugin 2.2.6
Project:
Jenkins
Priority:
Minor
Reporter:
tobias schaber
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24869) POM_VERSION is not resetted
tobias schaber updated JENKINS-24869 POM_VERSION is not resetted Change By: tobias schaber (26/Sep/14 5:39 PM) Labels: maven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24869) POM_VERSION is not resetted
tobias schaber
created JENKINS-24869
POM_VERSION is not resetted
Issue Type:
Bug
Assignee:
Unassigned
Components:
maven
Created:
25/Sep/14 6:58 PM
Description:
Hi,
I'm currently facing an issue with the variable $POM_VERSION.
I perform the following operations:
1. Clean Workspace
2. Checkout from Git (including the pom with Version 1.0.0)
3. Execute Shell (or execute maven goal, both leads to the same result):
mvn versions:set -DnewVersion=${POM_VERSION}-${BUILD_NUMBER};
Now the POM-Version is set to e.g. 1.0.0-25.
4. Publish 1.0.0-25 to Nexus
So everything fine until now. I now Trigger the process the next time, but the variable $POM_VERSION still contains the value "1.0.0-25" from the last run, so the next artifact would be deployed as "1.0.0-25-26" and so on.
I tried many things line unsetting the variables or copying them into other temp variables but I did not found a solution for this.
Could you please check if POM_VERSION could be resetted at the beginning?
Kind regards,
Tobias
Environment:
Jenkins 1.581
Maven 3.0.5
Project:
Jenkins
Priority:
Minor
Reporter:
tobias schaber
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24869) POM_VERSION is not resetted
tobias schaber assigned JENKINS-24869 to Unassigned POM_VERSION is not resetted Automatic assign. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-24800) docker plugin accept variables in pull image
tobias schaber created JENKINS-24800 docker plugin accept variables in pull image Issue Type: Improvement Assignee: vjuranek Components: docker-build-step Created: 22/Sep/14 11:59 AM Description: When I tried to pass a (predefined) variable e.g. $APP_NAME or $TAG to the docker command "Pull Image", it seems that this variables are not resolved. They occure on the remote console as $TAG and $APP_NAME. Is this a bug our could you maybe implement this? I'm trying to implement a generic deployment process thus I Need this Feature. Thank you! Kind regards, Tobias Environment: docker build step plugin Version 1.9 Jenkins Version 1.581 Project: Jenkins Labels: docker-build-step variables Priority: Minor Reporter: tobias schaber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
