[JIRA] (JENKINS-54571) Problem with jcasc compatibility plugin and job priority in Jenkins
Title: Message Title Cuong Tran commented on JENKINS-54571 Re: Problem with jcasc compatibility plugin and job priority in Jenkins Yeah, I was afraid you were going to say that. That's a shame jcasc can't handle everything. Thanks for the reply. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195354.1542018406000.2179.1567006440172%40Atlassian.JIRA.
[JIRA] (JENKINS-54571) Problem with jcasc compatibility plugin and job priority in Jenkins
Title: Message Title Cuong Tran commented on JENKINS-54571 Re: Problem with jcasc compatibility plugin and job priority in Jenkins Ljubisa Punosevac: were you able to figure this out? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195354.1542018406000.1523.1566969360196%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Cuong Tran commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines Was this property added to the agent or the master? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.19862.1563934380856%40Atlassian.JIRA.
[JIRA] (JENKINS-41240) naginator-plugin allows some build parameters to be changed via request parameters
Title: Message Title Cuong Tran commented on JENKINS-41240 Re: naginator-plugin allows some build parameters to be changed via request parameters I believe I need to supply all parameters to the "Rebuild Plugin" whereas I only want to overwrite some parameters, but I will take a closer look at the plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41240) naginator-plugin allows some build parameters to be changed via request parameters
Title: Message Title Cuong Tran updated an issue Jenkins / JENKINS-41240 naginator-plugin allows some build parameters to be changed via request parameters Change By: Cuong Tran Summary: naginator-plugin allows some build parameters to be changed via request parameters Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41240) naginator-plugin allows some parameters to be changed via request parameters
Title: Message Title Cuong Tran created an issue Jenkins / JENKINS-41240 naginator-plugin allows some parameters to be changed via request parameters Issue Type: Improvement Assignee: Nicolas De Loof Components: naginator-plugin Created: 2017/Jan/20 3:06 AM Priority: Minor Reporter: Cuong Tran I would like to add the option to overwrite some of the build parameters if they are passed via query parameters. I'm willing to submit a PR for the change but I would like know if this change is welcomed. My use case is I manage a large Jenkins farm and have an integration server that allows me to retry a large number of failed builds. I have a need to change the priority assigned to the retried builds. Thanks. Add Comment
[JIRA] (JENKINS-37821) Maven job fails with NPE when JDK is set to (System)
Title: Message Title Cuong Tran created an issue Jenkins / JENKINS-37821 Maven job fails with NPE when JDK is set to (System) Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Aug/30 6:24 PM Environment: Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06) maven-plugin 2.13 Priority: Major Reporter: Cuong Tran We recently upgraded to 1.651.31 and are not able run maven jobs due to the following exception: 23:57:33 Set build name. 23:57:33 New build name is '#1079-origin/geneva' 23:57:33 Parsing POMs 23:57:33 Established TCP socket on 58860 23:57:33 maven31-agent.jar already up to date 23:57:33 maven31-interceptor.jar already up to date 23:57:33 maven3-interceptor-commons.jar already up to date 23:57:33 [commons-test-parent] $ java -Xmx1024m -Xms512m ... 23:57:34 <===[JENKINS REMOTING CAPACITY]===>channel started 23:57:34 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com 23:57:34 java.lang.NullPointerException 23:57:34 at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:305) 23:57:34 at hudson.maven.ProcessCache.get(ProcessCache.java:236) 23:57:34 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:778) 23:57:34 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 23:57:34 at hudson.model.Run.execute(Run.java:1738) 23:57:34 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) 23:57:34 at hudson.model.ResourceController.execute(ResourceController.java:98) 23:57:34 at hudson.model.Executor.run(Executor.java:410) 23:57:34 project=hudson.maven.MavenModuleSet@489d6650[geneva/commons-test-master] It looks like this is the culprit: commit
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title Cuong Tran updated an issue Jenkins / JENKINS-36568 workflow script node step cannot trigger build on specific node Change By: Cuong Tran Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title Cuong Tran commented on JENKINS-36568 Re: workflow script node step cannot trigger build on specific node It doesn't work the way you think. Try the following: build job: 'test_job', parameters: [ [$class: 'LabelParameterValue', name: 'node', label: 'tester1'], ] build job: 'test_job', parameters: [ [$class: 'LabelParameterValue', name: 'node', label: 'tester2'], ] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title Cuong Tran edited a comment on JENKINS-36568 Re: workflow script node step cannot trigger build on specific node It doesn't work the way you think. Try the following:build job: 'test_job', parameters: [ [$class: 'LabelParameterValue', name: 'node', label: 'tester1'] , ] build job: 'test_job', parameters: [ [$class: 'LabelParameterValue', name: 'node', label: 'tester2'] , ] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-plugin] (JENKINS-33140) Git plugin doesn't use refspec on the first clone/fetch
Title: Message Title Cuong Tran updated an issue Jenkins / JENKINS-33140 Git plugin doesn't use refspec on the first clone/fetch Change By: Cuong Tran Our repositories have lots of references and we only need to build from a single branch from each job. For example, I have a job with refspec +refs/heads/master:refs/remotes/origin/master. On the first clone, it does the following:Cloning the remote Git repositoryUsing shallow cloneAvoid fetching tagsCloning repository https://github.com/foo.git > git init /tmp/jenkins/slave1/workspace/sample/smoke-test # timeout=10Fetching upstream changes from https://github.com/foo.git > git --version # timeout=10 > git -c core.askpass=true fetch --no-tags --progress https://github.com/foo.git +refs/heads/* * :refs/remotes/origin/* * --depth=1 # timeout=10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-33140) Git plugin doesn't use refspec on the first clone/fetch
Title: Message Title Cuong Tran created an issue Jenkins / JENKINS-33140 Git plugin doesn't use refspec on the first clone/fetch Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 25/Feb/16 12:23 AM Environment: Jenkins ver. 1.649 Git plugin 2.4.2 Priority: Minor Reporter: Cuong Tran Our repositories have lots of references and we only need to build from a single branch from each job. For example, I have a job with refspec +refs/heads/master:refs/remotes/origin/master. On the first clone, it does the following: Cloning the remote Git repository Using shallow clone Avoid fetching tags Cloning repository https://github.com/foo.git > git init /tmp/jenkins/slave1/workspace/sample/smoke-test # timeout=10 Fetching upstream changes from https://github.com/foo.git > git --version # timeout=10 > git -c core.askpass=true fetch --no-tags --progress https://github.com/foo.git +refs/heads/:refs/remotes/origin/ --depth=1 # timeout=10
[JIRA] [m2release] (JENKINS-11466) reenable ability to let maven decide the versioning
Cuong Tran commented on JENKINS-11466 reenable ability to let maven decide the versioning Is there a workaround for this? 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.
