[JIRA] (JENKINS-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-40351 JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed 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-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page
Title: Message Title Michael Clarke started work on JENKINS-40351 Change By: Michael Clarke Status: Open In Progress 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-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40351 Re: JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page Code changed in jenkins User: Michael Clarke Path: README.md src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure.jelly src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_es.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_fr.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_pt.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_pt_BR.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_zh_TW.properties http://jenkins-ci.org/commit/jenkins-test-harness/1f91370e5de270bc79e1b14b3558dfd92672b4e5 Log: [FIXED JENKINS-40351] provide missing config page 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-12480) Build step that runs multiple jobs in parallel, and blocks until all are complete
Title: Message Title Kunal W closed an issue as Not A Defect Check the attached screenshot and configure the job. Jenkins / JENKINS-12480 Build step that runs multiple jobs in parallel, and blocks until all are complete Change By: Kunal W Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-40075) Add support for multi-branch pipeline builds
Title: Message Title Srivardhan Hebbar resolved as Fixed office365ConnectorSend command can be used to send notifications from inside pipeline script. The support has been added to the plugin in the revision 2.0. The same has been updated in the wiki. Jenkins / JENKINS-40075 Add support for multi-branch pipeline builds Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-40342) No way to specify in the UI the network/IP address to use for SSH
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40342 Re: No way to specify in the UI the network/IP address to use for SSH Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/pom.xml jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsBuildWrapper.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsLauncher.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlave.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate.java jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/config.jelly jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/help-preferredAddress.html jclouds-plugin/src/test/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplateTest.java http://jenkins-ci.org/commit/jclouds-plugin/fc590e17533d693e9b7727336c744f280c832213 Log: Fixes JENKINS-40342 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-40342) No way to specify in the UI the network/IP address to use for SSH
Title: Message Title Fritz Elfert commented on JENKINS-40342 Re: No way to specify in the UI the network/IP address to use for SSH Ok, I have something to test for you: https://jenkins.ci.cloudbees.com/job/plugins/job/jclouds-plugin/304/org.jenkins-ci.plugins$jclouds-jenkins/artifact/org.jenkins-ci.plugins/jclouds-jenkins/2.12-SNAPSHOT/jclouds-jenkins-2.12-SNAPSHOT.hpi This adds a new Textfield "Preferred Address" in the Advanced Settings of the template. There you can enter an address/prefix and that should then match one of the node's IP-Addresses. Please report back if that fits your needs (or with any further suggestions). If everything is ok for you, I then will release v 2.12 with that change. Cheers -Fritz 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-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-40251 Dependency Check trend graphs and related values are not shown Change By: Steve Springett Assignee: Steve Springett 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-40353) Bitbucket OAuth plugin - java.lang.NullPointerException on login
Title: Message Title Colin Kennedy updated an issue Jenkins / JENKINS-40353 Bitbucket OAuth plugin - java.lang.NullPointerException on login Change By: Colin Kennedy Summary: Bitbucket OAuth plugin - java.lang.NullPointerException on login 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-30782) Failed to read environment variable table error
Title: Message Title Oleg Nenashev commented on JENKINS-30782 Re: Failed to read environment variable table error The issue still exists from what I see 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-40356) NPE on p4 polling
Title: Message Title
Matthew Hall updated an issue
Jenkins / JENKINS-40356
NPE on p4 polling
Change By:
Matthew Hall
{noformat}Started on Dec 9, 2016 4:47:00 PMP4: Polling on: master with:build-master-b-anonymizer... p4 client -o build-master-b-anonymizer +... p4 info +P4 Task: establishing connection server: p4build.engr .tivo.com :1666... node: jmtest .tivo.com P4 Task: attempt: 1P4 Task: failed: java.lang.NullPointerExceptionP4 Task: failed: java.lang.NullPointerExceptionFATAL: AbortedDone. Took 4.6 secNo changes{noformat}
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-40353) java.lang.NullPointerException on login
Title: Message Title Colin Kennedy created an issue Jenkins / JENKINS-40353 java.lang.NullPointerException on login Issue Type: Bug Assignee: Unassigned Components: bitbucket-oauth-plugin Created: 2016/Dec/09 10:03 PM Priority: Blocker Reporter: Colin Kennedy Jenkins 2.19.4 Running in Docker Mapping port 80:8080 in docker. http only (testing this locally). java.lang.NullPointerException at org.acegisecurity.providers.AbstractAuthenticationToken.equals(AbstractAuthenticationToken.java:107) at jenkins.security.NonSerializableSecurityContext.equals(NonSerializableSecurityContext.java:62) at org.eclipse.jetty.server.session.AbstractSession.callSessionAttributeListeners(AbstractSession.java:529) at org.eclipse.jetty.server.session.AbstractSession.changeAttribute(AbstractSession.java:513) at org.eclipse.jetty.server.session.AbstractSession.setAttribute(AbstractSession.java:461) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.storeSecurityContextInSession(HttpSessionContextIntegrationFilter.java:408) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:264) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at
[JIRA] (JENKINS-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page
Title: Message Title Michael Clarke started work on JENKINS-40351 Change By: Michael Clarke Status: Reopened In Progress 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-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page
Title: Message Title Michael Clarke reopened an issue Jenkins / JENKINS-40351 JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page Change By: Michael Clarke Resolution: Fixed Status: Resolved Reopened 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-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page
Title: Message Title Michael Clarke assigned an issue to Michael Clarke Jenkins / JENKINS-40351 JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page Change By: Michael Clarke Assignee: Oliver Gondža Michael Clarke 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-40355) P4 hangs on reconcile call
Title: Message Title Brian Collum created an issue Jenkins / JENKINS-40355 P4 hangs on reconcile call Issue Type: Bug Assignee: Unassigned Attachments: jenkins.p4crash.dump Components: p4-plugin Created: 2016/Dec/10 12:33 AM Environment: Windows 10 Pro 64-bit Jenkins 2.19.4 P4-Plugin 1.4.10 java version "1.8.0_111" Java(TM) SE Runtime Environment (build 1.8.0_111-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode) Priority: Critical Reporter: Brian Collum It seems the p4 plugin is simply hung on this p4 command. This is the second time it has happened, the first time was probably about two months ago (don't have logs from that time). We usually have at least one build occur every day, if not multiple. So it seems very infrequent but when it does happen, hitting the 'x' to cancel the build does not affect it and that Jenkins executor stays hung. So my only course of action that I know of is to kill the Jenkins service and restart it. Here is the last output on the Jenkins console: P4 Task: reverting all pending and shelved revisions. ... p4 revert C:\Jenkins\jobs\Sepac_x.58\workspace\buildType\standard\osType\linux\spec___ - p4 revert C:\Jenkins\jobs\Sepac_x.58\workspace\buildType\standard\osType\linux\specialBuild\none/... C:\Jenkins\jobs\Sepac_x.58\workspace\buildType\standard\osType\linux\specialBuild\none/... - file(s) not opened on this client. ... rm
[JIRA] (JENKINS-40356) NPE on p4 polling
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-40356 NPE on p4 polling Change By: Matthew Hall Environment: jdk 1.8.0_92, centos 5.8 jenkins master , p4 plugin 1.4.11 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-40356) NPE on p4 polling
Title: Message Title Matthew Hall created an issue Jenkins / JENKINS-40356 NPE on p4 polling Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Dec/10 12:47 AM Environment: jdk 1.8.0_92, centos 5.8 jenkins master Priority: Critical Reporter: Matthew Hall Started on Dec 9, 2016 4:47:00 PM P4: Polling on: master with:build-master-b-anonymizer ... p4 client -o build-master-b-anonymizer + ... p4 info + P4 Task: establishing connection. ... server: p4build.engr.tivo.com:1666 ... node: jmtest.tivo.com P4 Task: attempt: 1 P4 Task: failed: java.lang.NullPointerException P4 Task: failed: java.lang.NullPointerException FATAL: Aborted Done. Took 4.6 sec No changes Add Comment
[JIRA] (JENKINS-37272) With Jenkins 2.x Popups are empty
Title: Message Title
Dan Alvizu commented on JENKINS-37272
Re: With Jenkins 2.x Popups are empty
What version of the plugin are you running? The error ('X-Frame-Options' to 'sameorigin'.) seems to indicate jenkins is self-configured to use a different URL than the one you are accessing
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-40279) Disabling of Jenkins setup wizard not working as expected
Title: Message Title Daniel Beck commented on JENKINS-40279 Re: Disabling of Jenkins setup wizard not working as expected When does this case normally happen? Note that this method never returns INITIAL_SECURITY_SETUP without passing the shouldNotRun, so that shouldn't matter. But the condition you point to evaluates to true iff the .last_exec_version file is empty or contains the version 0.0 OR the JENKINS_HOME/config.xml doesn't exist or contains the version 1.0, indicating the global configuration has never before been saved. The latter is a heuristic to determine whether it's a new install or an existing one, and assumes that all actual Jenkins use involved someone clicking 'Save' on Configure Jenkins at least once (and if not, they're probably not too opposed to seeing a wizard once). Similar issues where this issue have been touched upon/mentioned/seen: One motivated implementing support for the system property you're setting to skip the install wizard, the other is about restoring an accidentally closed upgrade wizard. Neither is really relevant here. 2) Suppressing the Upgrade Wizard doesn't work using "session variable" -Djenkins.install.UpgradeWizard.show=false Well, yes, because it doesn't check the system property by that name, so setting it doesn't do anything. This feature simply does not exist, period, and both the documentation and me were wrong. Feel free to file a New Feature request for this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40281 Re: No Badge shown, Exception build.badgeActions depending on KeepBuildForever Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Run.java test/src/test/java/hudson/model/RunTest.java http://jenkins-ci.org/commit/jenkins/5c79beb3efc0058d38a36a302362e69625231377 Log: [FIXED JENKINS-40281] Do not try to mutate the result of getActions(Class). 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-39565) Global function with no parameters silently ignored when called without parenthesis
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39565 Re: Global function with no parameters silently ignored when called without parenthesis Code changed in jenkins User: R. Tyler Croy Path: content/doc/book/pipeline/shared-libraries.adoc http://jenkins-ci.org/commit/jenkins.io/afda67637c8a2f4764c458711ae41241e2766a4a Log: Clarify in the Shared Libraries section that "steps" in Shared Libraries are just variables Basically, the end-user can pretend that they're just like other "steps" but in truth we're using some Groovy invocation magic which means parameterless invocation doesn't work in the same manner as a real step. Fixes JENKINS-39565 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-40356) NPE on p4 polling
Title: Message Title
Matthew Hall edited a comment on JENKINS-40356
Re: NPE on p4 polling
This is from the jenkins.log : {noformat}Dec 09, 2016 4:51:01 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTaskSEVERE: P4 Task: attempt: 1java.lang.NullPointerException at org.jenkinsci.plugins.p4.client.ClientHelper.listHaveChanges(ClientHelper.java:1034) at org.jenkinsci.plugins.p4.tasks.PollTask.task(PollTask.java:52) at org.jenkinsci.plugins.p4.tasks.AbstractTask.tryTask(AbstractTask.java:209) at org.jenkinsci.plugins.p4.tasks.PollTask.invoke(PollTask.java:41) at org.jenkinsci.plugins.p4.tasks.PollTask.invoke(PollTask.java:25) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at org.jenkinsci.plugins.p4.PerforceScm.pollWorkspace(PerforceScm.java:352) at org.jenkinsci.plugins.p4.PerforceScm.compareRemoteRevisionWith(PerforceScm.java:297) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:391) at hudson.scm.SCM.poll(SCM.java:408) at hudson.model.AbstractProject._poll(AbstractProject.java:1460) at hudson.model.AbstractProject.poll(AbstractProject.java:1363) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:528) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:574) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Dec 09, 2016 4:51:04 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTaskWARNING: P4 Task: failed: java.lang.NullPointerException{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows
Title: Message Title Paul Londino edited a comment on JENKINS-16176 Re: ShiningPanda PATH update uses wrong separator on Windows I have encountered this bug as well. It's not trivial to troubleshoot unless you stumble upon this issue, and it's not an uncommon problem to want to test Python code across Windows and Linux , which necessitates a mismatch in the OS between the master and the slave . 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-16176) ShiningPanda PATH update uses wrong separator on Windows
Title: Message Title Paul Londino commented on JENKINS-16176 Re: ShiningPanda PATH update uses wrong separator on Windows I have encountered this bug as well. It's not trivial to troubleshoot unless you stumble upon this issue, and it's not an uncommon problem to want to test Python code across Windows and Linux. 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-25136) Build pipeline crashes after upgrading from 1.4.2 to 1.4.3.
Title: Message Title Dan Alvizu closed an issue as Won't Fix Closing out - this is a very old and unsupported version of the plugin. Current version is 1.5.6 Jenkins / JENKINS-25136 Build pipeline crashes after upgrading from 1.4.2 to 1.4.3. Change By: Dan Alvizu Status: Open Closed Assignee: Dan Alvizu Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-12480) Build step that runs multiple jobs in parallel, and blocks until all are complete
Title: Message Title Kunal W updated an issue Jenkins / JENKINS-12480 Build step that runs multiple jobs in parallel, and blocks until all are complete Change By: Kunal W Attachment: Screen Shot 2016-12-09 at 5.48.19 PM.png 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-40354) Support managing a Helix Graph Depot workspace
Title: Message Title Kuntal Das created an issue Jenkins / JENKINS-40354 Support managing a Helix Graph Depot workspace Issue Type: New Feature Assignee: Paul Allen Components: p4-plugin Created: 2016/Dec/09 11:09 PM Priority: Major Reporter: Kuntal Das Why? Perforce is introducing a separate type of depot, called Graph Depot, that will host git repositories. Perforce announced this in their last user conference, Merge 2016. With the use of the filespec view of a Perforce workspace, this will allow users to build off of multiple git repositories and/or slices of a git repo(narrow cloning) We need support in the P4 Jenkins tool to be able to create, manage & build off of this type of depot. What: Build: P4 Jenkins should be able to build off of a single GD from a single workspace. P4 Jenkins should be able to build off of a single GD from a single workspace of type graph, that may contain one or more git repos @ HEAD => the latest reference of all the repos in the GD @ a specific branch. That branch may apply to one ore more repos within the Graph Depot @ a
[JIRA] (JENKINS-30351) Plain text timing entries in build log file
Title: Message Title Steven G Brown commented on JENKINS-30351 Re: Plain text timing entries in build log file Rather than making two HTTP requests, you could have the timestamps URL provide the console text along with the timestamps when a certain query parameter is used. This would allow the log file of a single build to be inspected. This has been implemented as of Timestamper 1.8. 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-12480) Build step that runs multiple jobs in parallel, and blocks until all are complete
Title: Message Title Kunal W commented on JENKINS-12480 Re: Build step that runs multiple jobs in parallel, and blocks until all are complete We have to mention all the jobs in one step. Add all the jobs, separated by comma, in "Projects to build". Then check "Block until the triggered projects finish their builds" Works for me. 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-40356) NPE on p4 polling
Title: Message Title Matthew Hall commented on JENKINS-40356 Re: NPE on p4 polling Dec 09, 2016 4:51:01 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask SEVERE: P4 Task: attempt: 1 java.lang.NullPointerException at org.jenkinsci.plugins.p4.client.ClientHelper.listHaveChanges(ClientHelper.java:1034) at org.jenkinsci.plugins.p4.tasks.PollTask.task(PollTask.java:52) at org.jenkinsci.plugins.p4.tasks.AbstractTask.tryTask(AbstractTask.java:209) at org.jenkinsci.plugins.p4.tasks.PollTask.invoke(PollTask.java:41) at org.jenkinsci.plugins.p4.tasks.PollTask.invoke(PollTask.java:25) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at org.jenkinsci.plugins.p4.PerforceScm.pollWorkspace(PerforceScm.java:352) at org.jenkinsci.plugins.p4.PerforceScm.compareRemoteRevisionWith(PerforceScm.java:297) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:391) at hudson.scm.SCM.poll(SCM.java:408) at hudson.model.AbstractProject._poll(AbstractProject.java:1460) at hudson.model.AbstractProject.poll(AbstractProject.java:1363) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:528) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:574) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Dec 09, 2016 4:51:04 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask WARNING: P4 Task: failed: java.lang.NullPointerException Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40356) NPE on p4 polling
Title: Message Title Matthew Hall commented on JENKINS-40356 Re: NPE on p4 polling Polling appears to work fine with the Pipeline jobs, but with the Freestyle Project, it appears broken. This seems odd. 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-36539) OK button disabled if project type chosen first
Title: Message Title Manuel Recena Soto commented on JENKINS-36539 Re: OK button disabled if project type chosen first This kind of issues should provide information about the web browser. 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-40331) Create a way to trigger build in pipeline
Title: Message Title aurelien leboulanger created an issue Jenkins / JENKINS-40331 Create a way to trigger build in pipeline Issue Type: Improvement Assignee: Robin Müller Attachments: Screen Shot 2016-12-09 at 10.48.23 AM.png Components: gitlab-plugin Created: 2016/Dec/09 9:54 AM Environment: gitlab-plugin and jenkins are up to date Priority: Minor Reporter: aurelien leboulanger Currently i'm not able to define the gitlab trigger build configuration in my pipeline definition file (Jenkinsfile); i have to set the configuration in the jenkins job. It will be nice to be able to define the configuration directly in the Jenkinsfile. Add Comment
[JIRA] (JENKINS-38514) CauseOfBlockage from QueueTaskDispatcher.canTake discarded
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38514 Re: CauseOfBlockage from QueueTaskDispatcher.canTake discarded Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Node.java core/src/main/java/hudson/model/Queue.java core/src/main/java/hudson/model/queue/CauseOfBlockage.java core/src/main/java/jenkins/model/queue/CompositeCauseOfBlockage.java core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/jenkins/model/queue/CompositeCauseOfBlockage/summary.jelly test/src/test/java/hudson/model/queue/QueueTaskDispatcherTest.java test/src/test/java/hudson/slaves/NodeCanTakeTaskTest.java http://jenkins-ci.org/commit/jenkins/8d23041d4b785947dee1bc02f54a41d86b59bdda Log: JENKINS-38514 Retain CauseOfBlockage from JobOffer (#2651) Converted to JenkinsRule. Improved messages from Node.canTake. [FIXED JENKINS-38514] BuildableItem needs to retain information from JobOffer about why it is neither blocked nor building. Converted to JenkinsRule. Found an existing usage of BecauseNodeIsNotAcceptingTasks. Original JENKINS-6598 test was checking behavior we want amended by JENKINS-38514. Ensure that a BuildableItem which is simply waiting for a free executor reports that as its CauseOfBlockage. Review comments from @oleg-nenashev. Add Comment
[JIRA] (JENKINS-6598) Let Node and NodeProperty have more control over whether a node can run a task
Title: Message Title SCM/JIRA link daemon commented on JENKINS-6598 Re: Let Node and NodeProperty have more control over whether a node can run a task Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Node.java core/src/main/java/hudson/model/Queue.java core/src/main/java/hudson/model/queue/CauseOfBlockage.java core/src/main/java/jenkins/model/queue/CompositeCauseOfBlockage.java core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/jenkins/model/queue/CompositeCauseOfBlockage/summary.jelly test/src/test/java/hudson/model/queue/QueueTaskDispatcherTest.java test/src/test/java/hudson/slaves/NodeCanTakeTaskTest.java http://jenkins-ci.org/commit/jenkins/8d23041d4b785947dee1bc02f54a41d86b59bdda Log: JENKINS-38514 Retain CauseOfBlockage from JobOffer (#2651) Converted to JenkinsRule. Improved messages from Node.canTake. [FIXED JENKINS-38514] BuildableItem needs to retain information from JobOffer about why it is neither blocked nor building. Converted to JenkinsRule. Found an existing usage of BecauseNodeIsNotAcceptingTasks. Original JENKINS-6598 test was checking behavior we want amended by JENKINS-38514. Ensure that a BuildableItem which is simply waiting for a free executor reports that as its CauseOfBlockage. Review comments from @oleg-nenashev. Add Comment
[JIRA] (JENKINS-34674) Support configurable Default Update center IDs
Title: Message Title Daniel Beck commented on JENKINS-34674 Re: Support configurable Default Update center IDs Oleg Nenashev PTAL: https://wiki.jenkins-ci.org/pages/diffpages.action?pageId=38929503=103088848 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-40332) Useless context for snippet generator in MBPL folder
Title: Message Title Daniel Beck commented on JENKINS-40332 Re: Useless context for snippet generator in MBPL folder Came up in https://botbot.me/freenode/jenkins/2016-12-08/?msg=77693236=8 until https://botbot.me/freenode/jenkins/2016-12-08/?msg=77694239=9 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-40228) Security config hides certain parts with 2.32
Title: Message Title Raul Arabaolaza commented on JENKINS-40228 Re: Security config hides certain parts with 2.32 Daniel Beck First of all thanks for your time. I am afraid I have explained myself poorly, the main point of this ticket is not reporting something that is not properly working but about two possible usability issues with the UI First, to be able to change or see the JNLP port I need to check the Enable security make the change, click save with the check enabled... to end in a UI that is not showing me my recent changes applied, i believe there is no point in hiding the JNLP port settings when security is not active Second, if I have a state based control like a checkbox that says Enable security I expect checking it to have some impact on security settings. Unchecking it disables security, then why checking it does not enable anything? As you say there is a proper technical explanation, but from the end user perspective that control is misleading. When you have a checkbox that says Enable something you expect it to actually enable something, but in this case that is not true. What I am trying to say is that if this check is not enough to enable security the label should not be Enable Security . IMHO what this check really does when checked is to show the Security settings UI, so the label should reflect that. If you guys do not agree with this what about at least showing some kind of message when saving without selecting a security realm informing the user that security can not be enabled with the selected configuration?? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title
Hendrik Brinkmann edited a comment on JENKINS-32650
Re: Make PerformancePublisher a SimpleBuildStep
I updated to Version Performance Plugin version 1.15 that added a new pipeline step {{performanceReport}} and the following problems occured (see also [Github #73|https : //github.com/jenkinsci/performance-plugin/pull/74]): # Missing PerformanceTrend in Job-View !missing_trend.PNG|thumbnail! # Duplicated Performance Report in Build-View (see attachment) !duplicated_report.PNG|thumbnail! # Snippet generator cannot handle double values of relative thresholds {code:groovy}performanceReport compareBuildPrevious: false, configType: 'MRT', errorFailedThreshold: 0, errorUnstableResponseTimeThreshold: '', errorUnstableThreshold: 0, failBuildIfNoResultFile: false, modeOfThreshold: false, modePerformancePerTestCase: true, modeThroughput: false, nthBuildNumber: 0, parsers: [], relativeFailedThresholdNegative: , relativeFailedThresholdPositive: , relativeUnstableThresholdNegative: , relativeUnstableThresholdPositive: {code}I had to replace {{}} manually by the correct double values.
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-19476) Jenkins sometime does not record build information on disk
Title: Message Title Viktor Pal edited a comment on JENKINS-19476 Re: Jenkins sometime does not record build information on disk I can still see this with Jenkins ver. 2.19.3.No related entries in the logs.It looks like as the thread just died and nothing recorded this. This does not affect all the jobs, it happens sporadically. 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-19476) Jenkins sometime does not record build information on disk
Title: Message Title Viktor Pal reopened an issue See last comment. Jenkins / JENKINS-19476 Jenkins sometime does not record build information on disk Change By: Viktor Pal Resolution: Incomplete Status: Resolved Reopened 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-40332) Useless context for snippet generator in MBPL folder
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-40332 Useless context for snippet generator in MBPL folder Issue Type: Bug Assignee: Unassigned Components: pipeline, workflow-multibranch-plugin Created: 2016/Dec/09 10:47 AM Labels: multibranch Priority: Minor Reporter: Daniel Beck When accessing a multi-branch pipeline's snippet generator, the context is the multibranch folder, not an individual pipeline job. This results in the triggers section for prooperties to have the folder's triggers, which are misleading to pipeline creators. This should show a branch pipeline's applicable triggers instead. Use case (i.e. "why not just access the branch project?"): Access to MBPL snippet generator before having Jenkinsfiles. Sort of a chicken/egg problem. Add Comment
[JIRA] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title Hendrik Brinkmann commented on JENKINS-32650 Re: Make PerformancePublisher a SimpleBuildStep I updated to Version 1.15 that added a new pipeline step performanceReport and the following problems occured: Missing PerformanceTrend in Job-View Duplicated Performance Report in Build-View (see attachment) Snippet generator cannot handle double values of relative thresholds Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml performanceReport compareBuildPrevious: false, configType: 'MRT', errorFailedThreshold: 0, errorUnstableResponseTimeThreshold: '', errorUnstableThreshold: 0, failBuildIfNoResultFile: false, modeOfThreshold: false, modePerformancePerTestCase: true, modeThroughput: false, nthBuildNumber: 0, parsers: [], relativeFailedThresholdNegative: Double>, relativeFailedThresholdPositive: Double>, relativeUnstableThresholdNegative: Double>, relativeUnstableThresholdPositive: Double> I had to replace manually by the correct double values. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title
James Femia commented on JENKINS-39174
Re: Help text for projectName does not describe all permitted values
It is also important to note that if the Multibranch Pipeline is searching in branch folders with forward slashes in the sub-job names (or any other url-encodable char), it generates sub-jobs with encoded names. Copying the artifacts from these projects require you to specify the folder path, followed by the url-encoded name of the job. This is logical in terms of being able to resolve Folders containing jobs in Jenkins, but may trip you up when writing groovy. e.g. if I have a Multibranch project called "MyBranches", with base of https://my.repo, and I tell it to search for branches in /branches/jamie/* and it finds /branches/jamie/a and /branches/jamie/b, copying artifacts from these jobs requires me to use /MyBranches/branches%2Fjamie%2Fa. As a side node on that, unless I am using java.net.URLEncoder wrong, I have to replace the output of encode + with %20 in order for the string to match the job name.
def job_name = '/MyBranches/' + java.net.URLEncoder.encode('branches/jamie/a', 'UTF-8').replace('+', '%20')
I also did not know that the Pipeline Syntax link from different pages affected the behaviour of the snippet generator.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You
[JIRA] (JENKINS-40330) Authentication via LDAP is set in Jenkins, but users cannot login
Title: Message Title qi song created an issue Jenkins / JENKINS-40330 Authentication via LDAP is set in Jenkins, but users cannot login Issue Type: Task Assignee: qi song Attachments: QQ截图20161209172317.jpg, QQ截图20161209172547.jpg, QQ截图20161209173009.jpg Components: ldap-plugin Created: 2016/Dec/09 9:32 AM Environment: java.runtime.version 1.8.0_91-b14 os.version 2.6.32-573.18.1.el6.x86_64 (centos6.7) ldap plugin 1.13 Jenkins ver. 2.19.4 Priority: Minor Reporter: qi song Why don't I configure the LDAP validation successful? I have no problem on Jenkins server use ldapsearch. But it can't verify configuration to Jenkins. How to solve this problem? help。 Add Comment
[JIRA] (JENKINS-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Art V commented on JENKINS-34276
Re: docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
If this helps anyone, for the last few months I've been running with these changes to the plugin to work around this issue..
diff --git a/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy b/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy
index 196ee39..13ac834 100644
--- a/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy
+++ b/src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy
@@ -86,9 +86,10 @@ class Docker implements Serializable {
}
}
-script.sh "docker build -t ${image} ${args}"
-script.dockerFingerprintFrom dockerfile: dockerfile, image: image, toolName: script.env.DOCKER_TOOL_NAME
-this.image(image)
+def buildImage = this.image(image)
+script.sh "docker build -t ${buildImage.imageName()} ${args}"
+script.dockerFingerprintFrom dockerfile: dockerfile, image: buildImage.imageName(), toolName: script.env.DOCKER_TOOL_NAME
+buildImage
}
}
@@ -114,12 +115,12 @@ class Docker implements Serializable {
public V inside(String args = '', Closure body) {
docker.node {
-if (docker.script.sh(script: "docker inspect -f . ${id}", returnStatus: true) != 0) {
+if (docker.script.sh(script: "docker inspect -f . ${imageName()}", returnStatus: true) != 0) {
// Not yet present locally.
// withDockerContainer requires the image to be available locally, since its start phase is not a durable task.
pull()
}
-docker.script.withDockerContainer(image: id, args: args, toolName: docker.script.env.DOCKER_TOOL_NAME) {
+docker.script.withDockerContainer(image: imageName(), args: args, toolName: docker.script.env.DOCKER_TOOL_NAME) {
body()
}
}
@@ -133,7 +134,7 @@ class Docker implements Serializable {
public Container run(String args = '', String command = "") {
docker.node {
-def container = docker.script.sh(script: "docker run -d${args != '' ? ' ' + args : ''} ${id}${command != '' ? ' ' + command : ''}", returnStdout: true).trim()
+def container = docker.script.sh(script: "docker run -d${args != '' ? ' ' + args : ''} ${imageName()}${command != '' ? ' ' + command : ''}", returnStdout: true).trim()
docker.script.dockerFingerprintRun containerId: container, toolName: docker.script.env.DOCKER_TOOL_NAME
new Container(docker, container)
}
@@ -154,7 +155,7 @@ class Docker implements Serializable {
docker.node {
def taggedImageName = toQualifiedImageName(parsedId.userAndRepo + ':' + tagName)
// TODO as of 1.10.0 --force is deprecated; for 1.12+ do not try it even once
-docker.script.sh "docker tag --force=${force} ${id} ${taggedImageName} || docker tag ${id} ${taggedImageName}"
+docker.script.sh "docker tag --force=${force} ${imageName()} ${taggedImageName} || docker tag ${imageName()} ${taggedImageName}"
return taggedImageName;
}
}
[JIRA] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title Hendrik Brinkmann updated an issue Jenkins / JENKINS-32650 Make PerformancePublisher a SimpleBuildStep Change By: Hendrik Brinkmann Attachment: duplicated_report.PNG 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-40304) Snippet generator does not generate valid code for ReverseBuildTrigger
Title: Message Title Daniel Beck commented on JENKINS-40304 Re: Snippet generator does not generate valid code for ReverseBuildTrigger I learned yesterday that the correct triggers only show up on a MBPL branch job's snippet generator, not on the global one or the one shown for the MBPL folder project. I'm going to report that as a bug as well. Nobody wants to see a snippet generator with triggers for a folder project that cannot have a pipeline… 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-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title Hendrik Brinkmann updated an issue Jenkins / JENKINS-32650 Make PerformancePublisher a SimpleBuildStep Change By: Hendrik Brinkmann Attachment: missing_trend.PNG 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-40228) Security config hides certain parts with 2.32
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40228 Security config hides certain parts with 2.32 Change By: Daniel Beck Labels: usability 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-36374) troubleshooting ldap authentication failure
Title: Message Title qi song commented on JENKINS-36374 Re: troubleshooting ldap authentication failure Create/Update a dedicated Logs recorder (LDAP) as explained in Jenkins Logging including the following list: hudson.security = ALL jenkins.security = ALL org.acegisecurity.ldap = ALL org.acegisecurity.providers.ldap = ALL Having done that, first test your AD settings and then try to log in with a LDAP user (“UserX”). reference https://support.cloudbees.com/hc/en-us/articles/204983360-How-to-diagnose-LDAP-integration-problems 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-33272) GitHub-specific SCMFileSystem
Title: Message Title Stephen Connolly commented on JENKINS-33272 Re: GitHub-specific SCMFileSystem yup https://github.com/jenkinsci/github-branch-source-plugin/pull/93 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-19476) Jenkins sometime does not record build information on disk
Title: Message Title Daniel Beck resolved as Incomplete More than two years later this should be a new bug report. Jenkins / JENKINS-19476 Jenkins sometime does not record build information on disk Change By: Daniel Beck Status: Reopened Resolved Resolution: Incomplete 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
[JIRA] (JENKINS-39690) Only 'Started' notifications are visible in Rocketchat
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39690 Re: Only 'Started' notifications are visible in Rocketchat Code changed in jenkins User: Martin Reinhardt Path: src/main/java/jenkins/plugins/rocketchatnotifier/ActiveNotifier.java src/main/java/jenkins/plugins/rocketchatnotifier/RocketChatNotifier.java http://jenkins-ci.org/commit/rocketchatnotifier-plugin/87f2d714304411c8ea3efcd96369840a983bef1c Log: feat(debugging): Improved logging see https://issues.jenkins-ci.org/browse/JENKINS-39690 Compare: https://github.com/jenkinsci/rocketchatnotifier-plugin/compare/a9f2c689fe82...87f2d7143044 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-39174) Help text for projectName does not describe all permitted values
Title: Message Title
James Femia edited a comment on JENKINS-39174
Re: Help text for projectName does not describe all permitted values
It is also important to note that if the Multibranch Pipeline is searching in branch folders with forward slashes in the sub-job names (or any other url-encodable char), it generates sub-jobs with encoded names. Copying the artifacts from these projects require you to specify the folder path, followed by the *url-encoded* name of the job. This is logical in terms of being able to resolve Folders containing jobs in Jenkins, but may trip you up when writing groovy.e.g. if I have a Multibranch project called "MyBranches", with base of {{https://my.repo}}, and I tell it to search for branches in {{/branches/jamie/*}} and it finds {{/branches/jamie/a}} and {{/branches/jamie/b}}, copying artifacts from these jobs requires me to use {{/MyBranches/branches%2Fjamie%2Fa}}.As a side node on that, unless I am using {{java.net.URLEncoder}} wrong, I have to replace the output of encode {{+}} with {{%20}} in order for the string to match the job name if it has spaces in the url path .{noformat}def job_name = '/MyBranches/' + java.net.URLEncoder.encode('branches/jamie/ a spaces in path ', 'UTF-8').replace('+', '%20'){noformat}I also did not know that the *Pipeline Syntax* link from different pages affected the behaviour of the snippet generator.
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
[JIRA] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title
Hendrik Brinkmann edited a comment on JENKINS-32650
Re: Make PerformancePublisher a SimpleBuildStep
I updated to Performance Plugin version 1.15 that added a new pipeline step {{performanceReport}} and the following problems occured (see also [Github #73|https://github.com/jenkinsci/performance-plugin/pull/74]): # Missing PerformanceTrend in Job-View !missing_trend.PNG|thumbnail! # Duplicated Performance Report in Build-View (see attachment) !duplicated_report.PNG|thumbnail! # Snippet generator cannot handle double values of relative thresholds {code: groovy java }performanceReport compareBuildPrevious: false, configType: 'MRT', errorFailedThreshold: 0, errorUnstableResponseTimeThreshold: '', errorUnstableThreshold: 0, failBuildIfNoResultFile: false, modeOfThreshold: false, modePerformancePerTestCase: true, modeThroughput: false, nthBuildNumber: 0, parsers: [], relativeFailedThresholdNegative: , relativeFailedThresholdPositive: , relativeUnstableThresholdNegative: , relativeUnstableThresholdPositive: {code}I had to replace {{}} manually by the correct double values.
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-39148) Implement a cleanup worker
Title: Message Title Pavel Janoušek commented on JENKINS-39148 Re: Implement a cleanup worker PR implements this partially - it tries to do a full cleanup cycle on Jenkins startup. However subject of this enhancement should be periodic cleanup, so leave this JIRA still open. 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-39148) Implement a cleanup worker
Title: Message Title Pavel Janoušek edited a comment on JENKINS-39148 Re: Implement a cleanup worker This [PR|https://github.com/jenkinsci/foreman-node-sharing-plugin/pull/35] implements this the enhancement partially - it tries to do a full cleanup cycle on Jenkins startup. However subject of this enhancement should be periodic cleanup, so leave this JIRA still open. 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-39148) Implement a cleanup worker
Title: Message Title Pavel Janoušek edited a comment on JENKINS-39148 Re: Implement a cleanup worker This [PR|https://github.com/jenkinsci/foreman-node-sharing-plugin/pull/35] implements this partially - it tries to do a full cleanup cycle on Jenkins startup. However subject of this enhancement should be periodic cleanup, so leave this JIRA still open. 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-36539) OK button disabled if project type chosen first
Title: Message Title Manuel Recena Soto commented on JENKINS-36539 Re: OK button disabled if project type chosen first I could not reproduce the issue described here by using Jenkins 2.19.3, the previous version where the fix was delivered. Steps Click on New item option Click on Pipeline job / project Enter the a name for this new job Change the focus from the form field The submit button is enable This introduces a clear regression related with the keyword navigation. I was working on it during several days: PR-2250. I invite you to watch the screencast provided there. 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-36539) OK button disabled if project type chosen first
Title: Message Title
Manuel Recena Soto edited a comment on JENKINS-36539
Re: OK button disabled if project type chosen first
I could not reproduce the issue described here by using Jenkins {{2.19.3}}, the previous version where the fix was delivered.h4. Steps# Click on _New item_ option# Click on _Pipeline_ job / project# Enter the a name for this new job# Change the focus from the form field# The submit button is enableThis introduces a *{color:#d04437} clear regression {color}* related with the keyword navigation. I was working on it during several days: PR-2250. I invite you to watch the screencast provided there. (flag)
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-40228) Security config hides certain parts with 2.32
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-40228 Security config hides certain parts with 2.32 Change By: Raul Arabaolaza h3. What incorrect behavior happened? If you disable global security and later try to enable it again or change the conf the security conf is not properly shown *EDIT: To further clarify this issue does not report anything broken but some (IMHO) usability issues with the current UI** First, to be able to change or see the JNLP port I need to check the _Enable security_ make the change, click save with the check enabled... to end in a UI that is not showing me my recent changes applied, *i believe there is no point in hiding the JNLP port settings when security is not active** Second, if I have a state based control like a checkbox that says _Enable security_ I expect checking it to have some impact on security settings. Unchecking it disables security, then why checking it does not enable anything? As you say there is a proper technical explanation, *but from the end user perspective that control is misleading*. When you have a checkbox that says _Enable something_ you expect it to actually enable something, but in this case that is not true. What I am trying to say is that if this check is not enough to enable security the label should not be _Enable Security_ . IMHO what this check really does when checked is to show the Security settings UI, so the label should reflect that. If you guys do not agree with this what about at least showing some kind of message when saving without selecting a security realm informing the user that security can not be enabled with the selected configuration?? h3. Environment * O.S.: _Ubuntu 14.04.5 LTS_* Jenkins Version: _2.32_* Web browser: _N/A_* JDK version: _JDK8_ h3. What was the expected outcome? To be able to modify and configure security settings, with new data being shownh3. What is the TestRail case or automated test filename where this bug was found? N/Ah3. Step by step to reproduce it # Start 2.32 war in a clean home folder# Disable Global security and save# Try to enable it again. Set for example a fixed JNLP port on 5, save without changing the security realm.# Open security configuration again, it seems that security is not enabled (due to not using a security realm I believe) and the JNLP port is hiddenh3. Extra comments *This is probably more a usability issue than a proper bug, so I created this issue only to inform and (if the team decides so) start a discussion*
[JIRA] (JENKINS-39148) Implement a cleanup worker
Title: Message Title Pavel Janoušek stopped work on JENKINS-39148 Change By: Pavel Janoušek Status: In Progress Open 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-36044) A test (disallowed DOCTYPE) fails due to a localization error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36044 Re: A test (disallowed DOCTYPE) fails due to a localization error Code changed in jenkins User: andrealaura Path: core/src/test/java/jenkins/xml/XMLUtilsTest.java http://jenkins-ci.org/commit/jenkins/ba2900b27dba97c70d2bdbce043b752907ea7ea3 Log: [FIX JENKINS-36044]: Added default locale to XMLUtilsTest so that it … (#2649) [FIX JENKINS-36044]: Added default locale to XMLUtilsTest so that it runs independent from the host OS locale. [FIX JENKINS-36044]: Cleanup default-locale after test, to avoid impact to other tests. [FIX JENKINS-36044]: Make test language indepedent. [FIX JENKINS-36044]: Cleanup unused imports. 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
[JIRA] (JENKINS-36044) A test (disallowed DOCTYPE) fails due to a localization error
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-36044 A test (disallowed DOCTYPE) fails due to a localization error Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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-40329) Ability to specify a default workspace on all nodes
Title: Message Title
Allan BURDAJEWICZ created an issue
Jenkins / JENKINS-40329
Ability to specify a default workspace on all nodes
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Dec/09 8:38 AM
Environment:
Jenkins 2.19.3 Pipeline 2.4
Priority:
Minor
Reporter:
Allan BURDAJEWICZ
It would be great if I had the ability to define a default workspace location for all nodes inside my pipeline. Example: I want to specify a default workspace for all nodes inside my pipeline. If I want to do this, I need to wrap the same kind of snippet for each node. For example:
node ('A') {
dir("${env.BUILD_NUMBER}") {
withEnv(["WORKSPACE=${env.WORKSPACE}/${env.BUILD_NUMBER}"]) {
// ...
}
}
}
node ('B') {
dir("${env.BUILD_NUMBER}") {
withEnv(["WORKSPACE=${env.WORKSPACE}/${env.BUILD_NUMBER}"]) {
// ...
}
}
}
node ('C') {
dir("${env.BUILD_NUMBER}") {
withEnv(["WORKSPACE=${env.WORKSPACE}/${env.BUILD_NUMBER}"]) {
// ...
}
}
}
[...]
This is redundant. The same applies to the `ws` step.
[JIRA] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title Hendrik Brinkmann updated an issue Jenkins / JENKINS-32650 Make PerformancePublisher a SimpleBuildStep Change By: Hendrik Brinkmann Attachment: missing_trend.PNG 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-40330) Authentication via LDAP is set in Jenkins, but users cannot login
Title: Message Title qi song updated an issue Jenkins / JENKINS-40330 Authentication via LDAP is set in Jenkins, but users cannot login Change By: qi song Issue Type: Task Bug 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-40334) Need to bypass security checks on Groovy scripts (full API)
Title: Message Title Philippe Nobili created an issue Jenkins / JENKINS-40334 Need to bypass security checks on Groovy scripts (full API) Issue Type: Bug Assignee: Unassigned Components: script-security-plugin Created: 2016/Dec/09 12:51 PM Environment: Jenkins 2.19.4, plugin version: 1.24 Priority: Minor Reporter: Philippe Nobili Suggestion: Provide a way to completely bypass the security checks on Groovy scripts in the plugin's configuration (not just a sandbox mode...). Rationale: For many internal uses of Jenkins, security is managed through permission access tables, there is no need for this extra burden, especially because it raises issues with DSL-generated projects (see below). Note on DSL Projects: If the DSL contains parametrized Groovy code, each generated Groovy code has to be approved individually, which is very difficult if at all possible to manage. Add Comment
[JIRA] (JENKINS-34389) starting parallel matrix jobs with dynamic axes causes in wrong build configuration
Title: Message Title Jan Bottek commented on JENKINS-34389 Re: starting parallel matrix jobs with dynamic axes causes in wrong build configuration Hi all, something new about this issue? Can i help by giving more analyze information? Thanks in advance Kind regards Jan 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-34674) Support configurable Default Update center IDs
Title: Message Title Oleg Nenashev commented on JENKINS-34674 Re: Support configurable Default Update center IDs LGTM, thanks! 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-40118) Many script approvals pending after upgrading Jenkins
Title: Message Title Philippe Nobili commented on JENKINS-40118 Re: Many script approvals pending after upgrading Jenkins Issue not related to Jenkins upgrade (as thought) but to the the Script security 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-40335) "Trigger builds remotely" not saved in Project Pipeline Configuration
Title: Message Title Daniel Wilmer updated an issue Jenkins / JENKINS-40335 "Trigger builds remotely" not saved in Project Pipeline Configuration Change By: Daniel Wilmer The "Trigger builds remotely" Token is not saved (similar to JENKINS-36451).Steps to reproduce:* create an new Multibranch Pipeline Job . * Fill all required information.* Under "Build Triggers" select "Trigger builds remotely (e.g., from scripts)" . * Enter a token.* Save.* Open the configuration again.* The "Trigger builds remotely" checkbox is not selected anymore.Luckily as a workaround we can use the Trigger "Periodically if not otherwise run". 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-40335) "Trigger builds remotely" not saved in Project Pipeline Configuration
Title: Message Title Daniel Wilmer created an issue Jenkins / JENKINS-40335 "Trigger builds remotely" not saved in Project Pipeline Configuration Issue Type: Bug Assignee: Unassigned Components: build-token-root-plugin Created: 2016/Dec/09 1:11 PM Priority: Critical Reporter: Daniel Wilmer The "Trigger builds remotely" Token is not saved (similar to JENKINS-36451). Steps to reproduce: create an new Multibranch Pipeline Job Fill all required information. Under "Build Triggers" select "Trigger builds remotely (e.g., from scripts)" Enter a token. Save. Open the configuration again. The "Trigger builds remotely" checkbox is not selected anymore. Luckily as a workaround we can use the Trigger "Periodically if not otherwise run".
[JIRA] (JENKINS-26828) Add support for installing the NodeJS windows msi
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26828 Re: Add support for installing the NodeJS windows msi Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/CPU.java src/main/java/jenkins/plugins/nodejs/tools/DetectionFailedException.java src/main/java/jenkins/plugins/nodejs/tools/InstallerPathResolver.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersion.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersionRange.java src/main/java/jenkins/plugins/nodejs/tools/Platform.java src/main/java/jenkins/plugins/nodejs/tools/pathresolvers/LatestInstallerPathResolver.java src/test/java/jenkins/plugins/nodejs/tools/InstallerPathResolversTest.java src/test/resources/updates/jenkins.plugins.nodejs.tools.NodeJSInstaller.json http://jenkins-ci.org/commit/nodejs-plugin/9038814957cff39ee5c66c4c170e18a6baa16be0 Log: JENKINS-26828 Add support for installing the NodeJS windows msi Remove unused old method. Update some old duplicate code from jenkins core code. Extend version with range capabilities to check which version has only an msi installer. 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-40333) catchError disables Script Approval
Title: Message Title Aleksey Malevaniy created an issue Jenkins / JENKINS-40333 catchError disables Script Approval Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Dec/09 11:45 AM Labels: plugin pipeline Priority: Minor Reporter: Aleksey Malevaniy While it works as intended (try-catch doesn't propagate `RejectedAccessException` for security plugin to be approved later) it's very confusing for beginner to understand why there is no new script candidate for approving at `In-process Script Approval` section. There are two ways to make it better add documentation note for catchError; optionally re-throw `RejectedAccessException` Add Comment
[JIRA] (JENKINS-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek created an issue Jenkins / JENKINS-40336 invalid login for second template in one vsphere cloud Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2016/Dec/09 1:26 PM Environment: Jenkins 2.19.1 Vsphere Plugin 2.14 Vsphere Server 5.5 Windows Server 2008 R2 Labels: plugin jenkins vsphere Priority: Major Reporter: Jan Bottek if i create a Vsphere Cloud and one template => check template is working fine. If i then duplicate the template entry and try "check template" on the second, i get the following error message Problem validating org.jenkinsci.plugins.vsphere.tools.VSphereException: com.vmware.vim25.InvalidLogin: The logon can not be completed due to an incorrect user name or password If i create another Vsphere Cloud and one template their, it is also working, only the second template is not working.
[JIRA] (JENKINS-32650) Make PerformancePublisher a SimpleBuildStep
Title: Message Title Hendrik Brinkmann updated an issue Jenkins / JENKINS-32650 Make PerformancePublisher a SimpleBuildStep Change By: Hendrik Brinkmann Attachment: missing_trend.PNG 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-40053) ResourceBundleUtilTest fails due to localization error
Title: Message Title Andrea Gerster started work on JENKINS-40053 Change By: Andrea Gerster Status: Open In Progress 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-19476) Jenkins sometime does not record build information on disk
Title: Message Title Viktor Pal commented on JENKINS-19476 Re: Jenkins sometime does not record build information on disk I can still see this with Jenkins ver. 2.19.3. No related entries in the logs. It looks like as the thread just died and nothing recorded this. 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-34610) Windows AMI in endless loop
Title: Message Title Peter Backx commented on JENKINS-34610 Re: Windows AMI in endless loop Thank you Brendan for this information. I also found another cause of connection issues: the Windows 10 server AMIs on Amazon will block incoming WinRM traffic from the public network by default (I think this is the default setting in Windows). This needs to be changed in the firewall rules. (BTW I would suggest to only allow traffic from the Jenkins master IP, either through the Windows firewall or the Amazon security group or both) 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-29130) RTC Polling broken when Proxy enabled
Title: Message Title David Jozis commented on JENKINS-29130 Re: RTC Polling broken when Proxy enabled Hi Lakshmi, Yes, we believe this issue was fixed in that version of the build toolkit. I'll close the issue. Thanks, David. 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-40340) Option to suppress changelong when getting Pipeline Jenkinsfile from GitHub SCM
Title: Message Title Cory Grubbs created an issue Jenkins / JENKINS-40340 Option to suppress changelong when getting Pipeline Jenkinsfile from GitHub SCM Issue Type: Improvement Assignee: Unassigned Components: workflow-aggregator-plugin Created: 2016/Dec/09 3:11 PM Priority: Critical Reporter: Cory Grubbs When pulling pipeline script from SCM, there is no way to suppress the changelog which is makes it difficult if not impossible to easily distinguish changelog items between changes to the script file and changes to the actual app source the pipeline is building. In this particular case I have a generic pipeline script stored in a controlled GitHub repository along with app specific properties files which are loaded to control what gets executed in the pipeline script. The pipeline script then pulls the actual application source code for the build from within it. No need for the changelog of the build to include entries from changes to the generic pipeline script nor the properties files. Only want it to include app code source changes. Add Comment
[JIRA] (JENKINS-40048) Multiple checkout with pipeline script with nested depot paths causes continous builds
Title: Message Title Paul Allen updated JENKINS-40048 Ready for release Jenkins / JENKINS-40048 Multiple checkout with pipeline script with nested depot paths causes continous builds Change By: Paul Allen Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Paul Allen updated JENKINS-37462 Ready for release Jenkins / JENKINS-37462 Polling breaks with multiple slaves with own workspace Change By: Paul Allen Status: In Review Resolved Resolution: Fixed 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-38401) Jekinsfile Changelist number doesn't get updated when using pipeline Script from SCM.
Title: Message Title Paul Allen updated JENKINS-38401 Ready for release Jenkins / JENKINS-38401 Jekinsfile Changelist number doesn't get updated when using pipeline Script from SCM. Change By: Paul Allen Status: In Review Resolved Resolution: Fixed 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
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title Paul Allen updated JENKINS-39652 Ready for release Jenkins / JENKINS-39652 Add support for polling multiple checkouts with pipeline scripts Change By: Paul Allen Status: In Review Resolved Resolution: Fixed 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-40319) Add github Users as committers to blackduck-hub-plugin
Title: Message Title James Richard commented on JENKINS-40319 Re: Add github Users as committers to blackduck-hub-plugin Daniel Beck We would like to release to the Jenkins update center, I am attempting to create a PR to add the plugin-blackduck-hub.yml but I do not have permission to create a branch on that repo. Can you add me as a committer to that repo? 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-29130) RTC Polling broken when Proxy enabled
Title: Message Title David Jozis closed an issue as Fixed Jenkins / JENKINS-29130 RTC Polling broken when Proxy enabled Change By: David Jozis Status: Open Closed Resolution: Fixed 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-40339) Jenkins parallel pipeline: All subroutine calls in parameter blocks pass arguments from last block
Title: Message Title
Sascha Vujevic updated an issue
Jenkins / JENKINS-40339
Jenkins parallel pipeline: All subroutine calls in parameter blocks pass arguments from last block
Change By:
Sascha Vujevic
We are using a goovy-script in a parallel step and using an external method. I am expecting the parameter value dumped in [aaa] to be 'aaa', not 'eee'.{code:java}def build_if_needed(project) { println "build_if_needed: $project" // ultimately this will kick off a build job...}parallel ( aaa : { build_if_needed('aaa')}, bbb : { build_if_needed('bbb')}, ccc : { build_if_needed('ccc')}, ddd : { build_if_needed('ddd')}, eee : { build_if_needed('eee')}){code}The result is:{code:java}[Pipeline] parallel[Pipeline] [aaa] { (Branch: aaa)[Pipeline] [bbb] { (Branch: bbb)[Pipeline] [ccc] { (Branch: ccc)[Pipeline] [ddd] { (Branch: ddd)[Pipeline] [eee] { (Branch: eee)[Pipeline] [aaa] echo[aaa] build_if_needed: eee[Pipeline] [aaa] }[Pipeline] [bbb] echo[bbb] build_if_needed: eee[Pipeline] [bbb] }[Pipeline] [ccc] echo[ccc] build_if_needed: eee[Pipeline] [ccc] }[Pipeline] [ddd] echo[ddd] build_if_needed: eee[Pipeline] [ddd] }[Pipeline] [eee] echo[eee] build_if_needed: eee[Pipeline] [eee] }[Pipeline] // parallel[Pipeline] End of PipelineFinished: SUCCESS{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40339) Jenkins parallel pipeline: All subroutine calls in parameter blocks pass arguments from last block
Title: Message Title
Sascha Vujevic updated an issue
Jenkins / JENKINS-40339
Jenkins parallel pipeline: All subroutine calls in parameter blocks pass arguments from last block
Change By:
Sascha Vujevic
We are using a goovy-script in a parallel step and using a an external method.am expecting the parameter value dumped in [aaa] to be 'aaa', not 'eee'.{code:java}def build_if_needed(project) { println "build_if_needed: $project" // ultimately this will kick off a build job...}parallel ( aaa : { build_if_needed('aaa')}, bbb : { build_if_needed('bbb')}, ccc : { build_if_needed('ccc')}, ddd : { build_if_needed('ddd')}, eee : { build_if_needed('eee')}){code}The result is:{code:java}[Pipeline] parallel[Pipeline] [aaa] { (Branch: aaa)[Pipeline] [bbb] { (Branch: bbb)[Pipeline] [ccc] { (Branch: ccc)[Pipeline] [ddd] { (Branch: ddd)[Pipeline] [eee] { (Branch: eee)[Pipeline] [aaa] echo[aaa] build_if_needed: eee[Pipeline] [aaa] }[Pipeline] [bbb] echo[bbb] build_if_needed: eee[Pipeline] [bbb] }[Pipeline] [ccc] echo[ccc] build_if_needed: eee[Pipeline] [ccc] }[Pipeline] [ddd] echo[ddd] build_if_needed: eee[Pipeline] [ddd] }[Pipeline] [eee] echo[eee] build_if_needed: eee[Pipeline] [eee] }[Pipeline] // parallel[Pipeline] End of PipelineFinished: SUCCESS{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.4.11 Jenkins / JENKINS-39652 Add support for polling multiple checkouts with pipeline scripts Change By: Paul Allen Status: Resolved Closed 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-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.4.11 Jenkins / JENKINS-37462 Polling breaks with multiple slaves with own workspace Change By: Paul Allen Status: Resolved Closed 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-40048) Multiple checkout with pipeline script with nested depot paths causes continous builds
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.4.11 Jenkins / JENKINS-40048 Multiple checkout with pipeline script with nested depot paths causes continous builds Change By: Paul Allen Status: Resolved Closed 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-38401) Jekinsfile Changelist number doesn't get updated when using pipeline Script from SCM.
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.4.11 Jenkins / JENKINS-38401 Jekinsfile Changelist number doesn't get updated when using pipeline Script from SCM. Change By: Paul Allen Status: Resolved Closed 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-39220) ECS Cluster drop-down does not show more than 100 ecs clusters
Title: Message Title Jason Riddle commented on JENKINS-39220 Re: ECS Cluster drop-down does not show more than 100 ecs clusters From my co-worker Marshall. The issue seems to be around the IAM permissions to ecs:listclusters. According to the documentation http://docs.aws.amazon.com/AmazonECS/latest/developerguide/IAMPolicyExamples.html, "The CreateCluster and ListClusters actions do not accept any resources, so the resource definition is set to * for all resources." 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-34610) Windows AMI in endless loop
Title: Message Title Brendan Stewart commented on JENKINS-34610 Re: Windows AMI in endless loop Ultimately, opposite of my previous comment, we ended up giving up on this plugin for various reasons. But, we did enable all WinRm ports, including secure as well. That wasn't the cause of this issue. Thank you for getting back though. We hope to try and use it again in the future. But for our configuration it just wasn't up to the task. Perhaps it is today though, through bug fixing. 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-40337) Support custom checkout scm behaviors
Title: Message Title Logan Glickfield created an issue Jenkins / JENKINS-40337 Support custom checkout scm behaviors Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Dec/09 2:19 PM Priority: Minor Reporter: Logan Glickfield As I understand it right now, if I specify an agent, it creates a node, runs checkout scm, and uses the same node/workspace for all of the stages? And if I specify agent: none, I have to create my own node in each stage, and re-run checkout scm for each stage? What I want to do is specify "Additional Behaviors" on the checkout step (currently using the workaround described here), but achieve the benefits of running it once on the top-level agent and re-using across all stages. Is there any way to achieve this? Either by specifying Additional Behaviors on the top-level pipeline, or allowing a user to override the implicit checkout scm that happens when agent is set? Thanks! Add Comment
[JIRA] (JENKINS-39410) Clover-Plugin crash (InvocationTargetException)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39410 Re: Clover-Plugin crash (InvocationTargetException) Code changed in jenkins User: Marek Parfianowicz Path: src/main/java/hudson/plugins/clover/CloverPublisher.java http://jenkins-ci.org/commit/clover-plugin/0591eeabb798f2fb656c2c391324216fbae4715f Log: JENKINS-39410: removed @stapler-constructor annotation from the CloverPublisher constructor, because stapler handles simple types only (primitive, strings but not CoverageTarget); binding request parameters using a set of StaplerRequest.getParameter calls, instead of deprecated StaplerRequest.bindParameters (which was failing on our annotated constructor); added null-check for failingMetrics field 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.
