[JIRA] [gitlab-plugin] (JENKINS-28090) gitlab plugin causing configure job option to fail
Title: Message Title
Ernesto Valero commented on JENKINS-28090
Re: gitlab plugin causing configure job option to fail
Same problem with Centos 6.6 with Jenkins 1.605
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/gitlab-plugin/WEB-INF/lib/gitlab-plugin-1.1.16.jar!/com/dabsquared/gitlabjenkins/GitLabPushTrigger/config.jelly:22:87: method getProjectBranches threw exception: org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: java.io.StringReader@89f3279; line: 1, column: 2] at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:46) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at
[JIRA] [jenkins-tracker] (JENKINS-31647) Options to Ignore changes in Externals, But need externals during checkout.
Title: Message Title Ilayda Akinalan updated an issue Jenkins / JENKINS-31647 Options to Ignore changes in Externals, But need externals during checkout. Change By: Ilayda Akinalan Labels: externals jenkins svn Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-31301) Jira Plugin - Rest Client add comment failures
Title: Message Title
Radek Antoniuk edited a comment on JENKINS-31301
Re: Jira Plugin - Rest Client add comment failures
curl -v should show connection headers and I don't see them here, also you can use \{code\} for code formatting or just attach a text file.Obviously you can remove the lines with Authentication.This is what I am seeing:{code}$ curl -v 'https://synegen.atlassian.net/rest/api/2/issue/SYN-123/comment' -X POST -d '{ "body": "This is a test."}' -u admin:admin -H 'X-Atlassian-Token: nocheck' -H 'Content-Type: application/json'* Hostname was NOT found in DNS cache* Trying 165.254.226.241...* Connected to synegen.atlassian.net (165.254.226.241) port 443 (#0)* successfully set certificate verify locations:* CAfile: none CApath: /etc/ssl/certs* SSLv3, TLS handshake, Client hello (1):* SSLv3, TLS handshake, Server hello (2):* SSLv3, TLS handshake, CERT (11):* SSLv3, TLS handshake, Server key exchange (12):* SSLv3, TLS handshake, Server finished (14):* SSLv3, TLS handshake, Client key exchange (16):* SSLv3, TLS change cipher, Client hello (1):* SSLv3, TLS handshake, Finished (20):* SSLv3, TLS change cipher, Client hello (1):* SSLv3, TLS handshake, Finished (20):* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256* Server certificate:* subject: C=US; ST=California; L=San Francisco; O=Atlassian Network Services, Inc.; CN=*.atlassian.net* start date: 2014-09-09 00:00:00 GMT* expire date: 2017-11-15 12:00:00 GMT* subjectAltName: synegen.atlassian.net matched* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA* SSL certificate verify ok.* Server auth using Basic with user 'admin'> POST /rest/api/2/issue/SYN-123/comment HTTP/1.1> Authorization: Basic YWRtaW46YWRtaW4=> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)> Host: synegen.atlassian.net> Accept: */*> Referer: > X-Atlassian-Token: nocheck> Content-Type: application/json> Content-Length: 28> * upload completely sent off: 28 out of 28 bytes< HTTP/1.1 401 Unauthorized* Server nginx is not blacklisted< Server: nginx< Date: Fri, 20 Nov 2015 13:02:58 GMT< Content-Type: text/html;charset=UTF-8< Transfer-Encoding: chunked< Connection: keep-alive< X-AREQUESTID: 422x37052x1< X-ASEN: SEN-2400273< X-Seraph-LoginReason: OUT< X-Seraph-LoginReason: AUTHENTICATED_FAILED< X-Seraph-LoginReason: AUTHENTICATED_FAILED< WWW-Authenticate: OAuth realm="https%3A%2F%2Fsynegen.atlassian.net"< X-ASESSIONID: 10w46rw< X-Content-Type-Options: nosniff< Set-Cookie: JSESSIONID=4319B388732910ADA095CC6DFDB955D7; Path=/; Secure; HttpOnly< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly< html content{code} Also, just curious, what works? You said hyperlinking does, but that is just fetching data from JIRA, do any things that actually do changes in JIRA work?
Add Comment
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title Ulli Hafner commented on JENKINS-31633 Re: Only first execution is tracked I don't want to remove maven support. I just want to remove the special handling of maven projects. Currently I have two classes, one for maven, one for freestyle. In the future I would merge these classes (or delete the maven class). This is how the warnings plug-in works: just one class for both project types. From the user perspective there is almost no difference. Disadvantages: 1) I can't (yet) read information from the pom. So you need to specify the filename pattern manually in the configuration section. 2) The findbugs plug-in shows up in the post build actions... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Title: Message Title James Nord updated an issue Jenkins / JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war Change By: James Nord Component/s: packaging Component/s: debian-package-builder-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
Title: Message Title Peter Pakos reopened an issue It's still happening for us with the most recent versions of Jenkins and the plugins. Dave Taddei, what versions have you tried it with? Jenkins / JENKINS-26303 Not compatible with Subversion plugin 2.5 Change By: Peter Pakos Resolution: Cannot Reproduce Status: Resolved Reopened Assignee: Kevin Bell Dave Taddei Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-31680) Use new bitbucket api to set if build success instead of add a comment
Title: Message Title Rubens M created an issue Jenkins / JENKINS-31680 Use new bitbucket api to set if build success instead of add a comment Issue Type: Improvement Assignee: Unassigned Components: bitbucket-pullrequest-builder-plugin Created: 20/Nov/15 2:22 PM Priority: Minor Reporter: Rubens M Would be nice if instead of posting many comments in the bitbucket pull-request, the plugin use the new build status API to set the build status, INPROGRESS, SUCCESSFUL, FAILED. http://blog.bitbucket.org/2015/11/18/introducing-the-build-status-api-for-bitbucket-cloud/ https://confluence.atlassian.com/bitbucket/buildstatus-resource-779295267.html Add Comment
[JIRA] [packaging] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Title: Message Title James Nord closed an issue as Won't Fix as per last comment this is a bug in the Debain projects repackage Jenkins and not in our Debian package Jenkins / JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war Change By: James Nord Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-31681) Build Name Setter plugin doesn't depend on Token Macro properly
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-31681 Build Name Setter plugin doesn't depend on Token Macro properly Issue Type: Bug Assignee: Lev Mishin Components: build-name-setter-plugin Created: 20/Nov/15 2:58 PM Environment: Jenkins 1.634, Linux Priority: Minor Reporter: R. Tyler Croy Install version 1.5.1 from the update center on a fresh install will result in the following error when I navigate to a Freestyle job configuration page: Nov 20, 2015 6:45:11 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.buildnameupdater.BuildNameUpdater$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/MacroEvaluationException at org.jenkinsci.plugins.buildnameupdater.BuildNameUpdater$DescriptorImpl.(BuildNameUpdater.java:179) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at
[JIRA] [envinject-plugin] (JENKINS-31682) Job archive directory is added to the front of the properties file path
Title: Message Title
Cam Spencer created an issue
Jenkins / JENKINS-31682
Job archive directory is added to the front of the properties file path
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
envinject-plugin, parameterized-trigger-plugin
Created:
20/Nov/15 3:14 PM
Environment:
Jenkins version 1.636 java.version 1.7.0_17 os.arch x86 os.name Windows Server 2008 R2 os.version 6.1 envinject 1.92.1
Priority:
Major
Reporter:
Cam Spencer
When we try to build another job using a properties file to set the parameters, the directory "C:\Program Files (x86)\Jenkins\jobs\jobName\builds\buildNum\archive\" is added to the front of the specified properties file. This same code was working with Jenkins 1.627, it stopped working after we upgraded to 1.636
Injecting Environment Variables
PROPSFULLFILENAME=${WORKSPACE}\triggeredjobvars.properties
Execute Windows Batch Command
@echo.
@echo Creating
[JIRA] [proc-cleaner-plugin] (JENKINS-31478) Attach ps output to the LOG and job console when error occurs, verify return code
Title: Message Title Pavel Janoušek commented on JENKINS-31478 Re: Attach ps output to the LOG and job console when error occurs, verify return code PR sent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-31501) Jenkins fails to connect to running emulator
Title: Message Title Alex Timmermann updated an issue Jenkins / JENKINS-31501 Jenkins fails to connect to running emulator Change By: Alex Timmermann Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31649) SECURITY-186 fix is too aggressive
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31649 Re: SECURITY-186 fix is too aggressive Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Queue.java http://jenkins-ci.org/commit/jenkins/46ef3a5776b9a60a1e5d364c29afda01fa09faed Log: Merge pull request #1919 from stephenc/jenkins-31649 [FIXED JENKINS-31649] Check should be against AccessControlled not Item Compare: https://github.com/jenkinsci/jenkins/compare/23276180209b...46ef3a5776b9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-16350) "logout" link doesn't work
Title: Message Title Leandro Lucarella commented on JENKINS-16350 Re: "logout" link doesn't work Yup, not really an option for private Jenkins instances... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31581) Generate config for a node condition
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31581 Re: Generate config for a node condition Code changed in jenkins User: eddyhub Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/RunConditionContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/condition/NodeCondition.groovy http://jenkins-ci.org/commit/job-dsl-plugin/cbc200e3f702b152eef2c471d288c2d2fcea5dcf Log: JENKINS-31581 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clang-scanbuild-plugin] (JENKINS-24498) Promoted builds plugin fails to execute automatic (end of build) promotions
Title: Message Title Emilio Escobar stopped work on JENKINS-24498 Change By: Emilio Escobar Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-31633) Only first execution is tracked
Title: Message Title C. S. commented on JENKINS-31633 Re: Only first execution is tracked Alright in this case I have solved it like here JENKINS-28746 . I have changed the phases of the different exceutions to be sure that the non breaker execution is executed at first. What would be the advantage to support only freetype? There are some plugins which are limited to maven projects, which can't be used together without creating an own analysis job in jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-31676) First git clone with http authentication
Title: Message Title Mark Waite resolved as Not A Defect Hudson bug reports should be submitted to the Hudson project. The Hudson project and the Jenkins project have diverged significantly since the Jenkins project was created. The git plugin has diverged significantly since the split. Both projects almost completely rewrote the git plugin, with each rewrite being independent of the other project. Jenkins / JENKINS-31676 First git clone with http authentication Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-31673) Broken reporting of exception
Title: Message Title Paul Millar created an issue Jenkins / JENKINS-31673 Broken reporting of exception Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 20/Nov/15 9:44 AM Environment: Jenkins ver. 1.638 Priority: Major Reporter: Paul Millar In hudson.tasks.junit.TestResult#parse (line 297), a DocumentException is caught and reported as a failing test. Unfortunately, the failing test yields a broken "Test Report" page. Selecting the '+' symbol expands the error, but results in a 404 not found, so the details of the stack-trace are unavailable. This affect is visible at this example. Cheers, Paul.
[JIRA] [job-dsl-plugin] (JENKINS-31674) Incomplete support for Mask Passwords Plugin
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-31674
Incomplete support for Mask Passwords Plugin
Change By:
Sam Gleske
Job DSL Plugin release 1.26 and later provides incomplete support for the Mask Passwords plugin. The support is incomplete because it doesn't allow you to define passwords. It's missing the core component that makes the plugin worth having.The workaround is to use the advanced configure block to implement the setting.{code}import hudson.util.SecretfreeStyleJob('example') { configure { project ->project / 'buildWrappers' / 'com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsBuildWrapper' / 'varPasswordPairs'() { 'varPasswordPair'(var: 'mypass', password: Secret.fromString('somepassword').getEncryptedValue())} } steps {shell 'echo \'somepassword\'' }}{code}Note: use of {{hudson.util.Secret}} is intentional to avoid the Job DSL plugin writing out the passwords in plain text to the XML job config. h3. XML Output{code}...
[JIRA] [core] (JENKINS-31649) SECURITY-186 fix is too aggressive
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31649 SECURITY-186 fix is too aggressive Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31649) SECURITY-186 fix is too aggressive
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31649 Re: SECURITY-186 fix is too aggressive Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Queue.java http://jenkins-ci.org/commit/jenkins/cf1fdf98e435b4c7df54f1a8e958d185f1a0f3d2 Log: [FIXED JENKINS-31649] Check should be against AccessControlled and Permission.READ The previous check was to narrow. We now check on AccessControlled (which is implemented by Item) We now also check on Permission.READ (which is the generic read permission) This should allow subtasks who's task may not be an Item to at least implement AccessControlled to alow visibility. There remains an open question as to whether tasks that are not AccessControlled should ever be visible in the UI Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-31676) First git clone with http authentication
Title: Message Title Hamid EL FAHSSI updated an issue Jenkins / JENKINS-31676 First git clone with http authentication Change By: Hamid EL FAHSSI Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-31677) Plugin incorrectly reports a successful connection to RunDeck server
Title: Message Title
Ioannis Mavroukakis created an issue
Jenkins / JENKINS-31677
Plugin incorrectly reports a successful connection to RunDeck server
Issue Type:
Bug
Assignee:
Vincent Behar
Components:
rundeck-plugin
Created:
20/Nov/15 11:18 AM
Environment:
Jenkins Version:1.596.2 RunDeck version:3.5.1
Priority:
Major
Reporter:
Ioannis Mavroukakis
The plugin incorrectly responds a successful connection and authentication to the server, eventhough the logs show otherwise:
Nov 20, 2015 11:07:53 AM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://my.server.com: The target server failed to respond
Nov 20, 2015 11:07:53 AM org.apache.http.impl.client.DefaultHttpClient tryExecute
[JIRA] [git-plugin] (JENKINS-31678) NullPointerException when using GitPublisher in release post build actions
Title: Message Title Marcus Klein created an issue Jenkins / JENKINS-31678 NullPointerException when using GitPublisher in release post build actions Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 20/Nov/15 11:29 AM Environment: Debian Wheezy running Jenkins 1.638 with git-plugin 2.4.0. Labels: git plugin exception Priority: Major Reporter: Marcus Klein Configure a job to use the Jenkins release plugin and use the Git publisher as release step after a successful release build. Tick the checkbox "Push only If Build Succeeds". Then a release build failes with the following NullPointerException: FATAL: null java.lang.NullPointerException at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:203) at hudson.plugins.release.ReleaseWrapper.executeBuildSteps(ReleaseWrapper.java:423) at hudson.plugins.release.ReleaseWrapper.access$300(ReleaseWrapper.java:99) at hudson.plugins.release.ReleaseWrapper$4.tearDown(ReleaseWrapper.java:370) at hudson.model.Build$BuildExecution.doRun(Build.java:173)
[JIRA] [clang-scanbuild-plugin] (JENKINS-24498) Promoted builds plugin fails to execute automatic (end of build) promotions
Title: Message Title Emilio Escobar assigned an issue to Unassigned Jenkins / JENKINS-24498 Promoted builds plugin fails to execute automatic (end of build) promotions Change By: Emilio Escobar Assignee: Emilio Escobar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated The plugin has some limited tests for the less commonly used protocols (ftp, rsync) and less commonly used authentication techniques (netrc file in the home directory of the Jenkins user). I consider those outside the scope of this change. It does not have a way of using the Jenkins credentials mechanism with those protocols as far as I can tell. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-31301) Jira Plugin - Rest Client add comment failures
Title: Message Title
Radek Antoniuk commented on JENKINS-31301
Re: Jira Plugin - Rest Client add comment failures
curl -v should show connection headers and I don't see them here, also you can use {code} for code formatting or just attach a text file. Obviously you can remove the lines with Authentication.This is what I am seeing:
$ curl -v 'https://synegen.atlassian.net/rest/api/2/issue/SYN-123/comment' -X POST -d '{ "body": "This is a test."}' -u admin:admin -H 'X-Atlassian-Token: nocheck' -H 'Content-Type: application/json'
* Hostname was NOT found in DNS cache
* Trying 165.254.226.241...
* Connected to synegen.atlassian.net (165.254.226.241) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Atlassian Network Services, Inc.; CN=*.atlassian.net
* start date: 2014-09-09 00:00:00 GMT
* expire date: 2017-11-15 12:00:00 GMT
* subjectAltName: synegen.atlassian.net matched
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.
* Server auth using Basic with user 'admin'
> POST /rest/api/2/issue/SYN-123/comment HTTP/1.1
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
> Host: synegen.atlassian.net
> Accept: */*
> Referer:
> X-Atlassian-Token: nocheck
> Content-Type: application/json
> Content-Length: 28
>
* upload completely sent off: 28 out of 28 bytes
< HTTP/1.1 401 Unauthorized
* Server nginx is not blacklisted
< Server: nginx
< Date: Fri, 20 Nov 2015 13:02:58 GMT
< Content-Type: text/html;charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< X-AREQUESTID: 422x37052x1
< X-ASEN: SEN-2400273
< X-Seraph-LoginReason: OUT
< X-Seraph-LoginReason: AUTHENTICATED_FAILED
< X-Seraph-LoginReason: AUTHENTICATED_FAILED
< WWW-Authenticate: OAuth realm="https%3A%2F%2Fsynegen.atlassian.net"
< X-ASESSIONID: 10w46rw
< X-Content-Type-Options: nosniff
< Set-Cookie: JSESSIONID=4319B388732910ADA095CC6DFDB955D7; Path=/; Secure; HttpOnly
< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
< Set-Cookie: studio.crowd.tokenkey=""; Domain=.synegen.atlassian.net; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly
<
html content
[JIRA] [junit-plugin] (JENKINS-31658) Plugin changes build result to UNSTABLE, despite all tests either passing or skipped
Title: Message Title Paul Millar commented on JENKINS-31658 Re: Plugin changes build result to UNSTABLE, despite all tests either passing or skipped A further symptom was that a Test Result showed the "junit.xml." as failing. Unfortunately, selecting the test result yielded no further information, but showed a 404 page not found error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-31658) Plugin changes build result to UNSTABLE, despite all tests either passing or skipped
Title: Message Title Paul Millar resolved as Fixed The problem turned out to be because the slave was running an older version of the swarm-slave jar file (v1.9). Upgrading the swarm-slave to v2.0 fixed the problem. Jenkins / JENKINS-31658 Plugin changes build result to UNSTABLE, despite all tests either passing or skipped Change By: Paul Millar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-31675) Allow setting a prefix for properties read from file
Title: Message Title João Cabrita created an issue Jenkins / JENKINS-31675 Allow setting a prefix for properties read from file Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger-plugin Created: 20/Nov/15 10:44 AM Priority: Minor Reporter: João Cabrita When using parameterized triggers with properties from a file, it would be nice to be able to set a prefix, to avoid name clashes. For example, I might have a set of modules and each produces a properties file with the same properties. If I want to aggregate those for downstream builds, there will be name clashes that could be avoided by specifying a prefix for properties in a given file, like: # moduleA.properties version=1.0.0 #would become moduleA.version # moduleB.properties version=2.0.0 #would become moduleB.version
[JIRA] [job-dsl-plugin] (JENKINS-31674) Incomplete support for Mask Passwords Plugin
Title: Message Title
Sam Gleske created an issue
Jenkins / JENKINS-31674
Incomplete support for Mask Passwords Plugin
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
20/Nov/15 10:44 AM
Environment:
Job DSL 1.40
Priority:
Minor
Reporter:
Sam Gleske
Job DSL Plugin release 1.26 and later provides incomplete support for the Mask Passwords plugin. The support is incomplete because it doesn't allow you to define passwords. It's missing the core component that makes the plugin worth having.
The workaround is to use the advanced configure block to implement the setting.
import hudson.util.Secret
freeStyleJob('example') {
configure { project ->
project / 'buildWrappers' / 'com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsBuildWrapper' / 'varPasswordPairs'() {
'varPasswordPair'(var: 'mypass', password: Secret.fromString('somepassword').getEncryptedValue())
}
}
steps {
shell 'echo \'somepassword\''
}
}
Note: use of hudson.util.Secret is intentional to avoid the Job DSL plugin writing out the passwords
[JIRA] [ldap-plugin] (JENKINS-29162) Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...
Title: Message Title James Nord commented on JENKINS-29162 Re: Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ... You can configure the plugin with multiple LDAP servers so to failover to a backup if the primary goes down. If you only have one LDAP server then I would recommend getting another one - (Steven - your company is not short of LDAP servers). There are current non Jenkins workarounds like using a service like MS AD LDS - solutions from other vendors apply also - but this does indeed add to the complexity of getting something like this working adds to support and are less than ideal. An API token should still work for script based access in order to reset some configuration - but there appears to be no API for Configure System or Configure Global Security that I could find that would allow you to change this. As for the 1 hour maximum (worth a different JIRA - but 3 days sounds a little excessive to me from a security perspective) - PRs welcome to this code Daniel Beck LDAP plugin should already cache this data (assuming you have already authenticated) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31581) Generate config for a node condition
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.41. Jenkins / JENKINS-31581 Generate config for a node condition Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deployment-notification-plugin] (JENKINS-28632) Workflow support for Deployment Notification trigger
Title: Message Title
Antonio Muñiz commented on JENKINS-28632
Re: Workflow support for Deployment Notification trigger
node {
unarchive 'bin/stuff'
sh 'scp bin/stuff root@puppethost:/production' // whatever
}
awaitDeployment('production')
This proposal splits deployment and wait steps in two separate consecutive instructions, what would happen if the deployment send the finish event notification *before* awaitDeployment started to listen for it?
Perhaps something like this would be safer:
awaitDeployment('production') {
node {
unarchive 'bin/stuff'
sh 'scp bin/stuff root@puppethost:/production' // whatever
}
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31674) Incomplete support for Mask Passwords Plugin
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-31674
Incomplete support for Mask Passwords Plugin
Change By:
Sam Gleske
Job DSL Plugin plugin release 1.26 and later provides incomplete support for the Mask Passwords plugin. The support is incomplete because it doesn't allow you to define passwords. It's missing the core component that makes the plugin worth having.The workaround is to use the advanced configure block to implement the setting.{code}import hudson.util.SecretfreeStyleJob('example') { configure { project ->project / 'buildWrappers' / 'com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsBuildWrapper' / 'varPasswordPairs'() { 'varPasswordPair'(var: 'mypass', password: Secret.fromString('somepassword').getEncryptedValue())} } steps {shell 'echo \'somepassword\'' }}{code}Note: use of {{hudson.util.Secret}} is intentional to avoid the Job DSL plugin writing out the passwords in plain text to the XML job config.h3. XML Output{code}...
[JIRA] [git-plugin] (JENKINS-31676) First git clone with http authentication
Title: Message Title Hamid EL FAHSSI created an issue Jenkins / JENKINS-31676 First git clone with http authentication Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 20/Nov/15 11:02 AM Priority: Minor Reporter: Hamid EL FAHSSI Hello, I am using http authentication to access the remote git repository. Jenkins and the git bare are actually on the same machine for now. The weird thing is that when I use the http address to access it I get a 'Could not clone git repository' error the first time, and then it works fine. But when I specify a local address to clone, it works perfectly. To handle the authentication, I have created a _netrc file containing the authentication requirements (machine name, login/password). When I try to clone the git repository in a command window it works fine and without problems. What I have seen is that, if the .git repository inside the workspace does not exist the build fails, but if it does it works. Can you please get back to me on how to solve that issue? For info, I am using Hudson version 2.2.0, Git-plugin 2.2.1. The exception trace is: -- Building on master Checkout:workspace / C:\Programs\SmartCDgeneration\HUDSON\jobs\GenerateGitVersion_Test_Clean_13\workspace - hudson.remoting.LocalChannel@b361f2 Using strategy: Default Checkout:workspace / C:\Programs\SmartCDgeneration\HUDSON\jobs\GenerateGitVersion_Test_Clean_13\workspace - hudson.remoting.LocalChannel@b361f2 Wiping out workspace first. Cloning the remote Git repository Cloning repository
[JIRA] [git-plugin] (JENKINS-31676) First git clone with http authentication
Title: Message Title Hamid EL FAHSSI commented on JENKINS-31676 Re: First git clone with http authentication All right. Thank you, I will redirect my report. Nice day. Bye. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-31647) Options to Ignore changes in Externals, But need externals during checkout.
Title: Message Title Ilayda Akinalan assigned an issue to olamy Jenkins / JENKINS-31647 Options to Ignore changes in Externals, But need externals during checkout. Change By: Ilayda Akinalan Assignee: olamy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Xavier Van Dessel commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated I fully agree with Mark and Sam comments regarding different protocols between main and submodule. Most installations will use a homogenuous approach. I would however recommend to add this requirement/limitation in the info box that opens for the new submodule authentication option. There are however still other (less commonly used) protocols which may require testing. Git supports ftp as a protocol using passwords. I have no idea whether the code changes between http(s) and ftp justify an explicit test setup. My test setup (BitBucket based) does not support it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31674) Incomplete support for Mask Passwords Plugin
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-31674 Incomplete support for Mask Passwords Plugin Change By: Daniel Spilker Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-24743) Findbug and PMD are broken in Jenkins 1.565.2
Title: Message Title Sylwia Kludacz commented on JENKINS-24743 Re: Findbug and PMD are broken in Jenkins 1.565.2 This problem has been resolved now and it was related to xerces on Jenkins server. There were two instances of the xercesImpl.jar file on the server, one in the endorsed directory and one in the ext directory. It looks like Jenkins was loading the one from the endorsed directory first, the endorsed directory didn’t have the xml-apis.jar file which has dependency links from the xercesImpl.jar library. By deleting the lib from the endorsed folder it resolved the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31581) Generate config for a node condition
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31581 Re: Generate config for a node condition Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/FlexiblePublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/ConditionalStepsContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/RunConditionContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/condition/NodeCondition.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/condition/RunConditionFactory.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/RunConditionContextSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/7c00084116322b12914c97ac88600dea8d98b1f6 Log: Merge branch 'JENKINS-31581' Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/b3ec98bbe508...7c0008411632 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clang-scanbuild-plugin] (JENKINS-31679) Remove unnecessary system.err logs
Title: Message Title Emilio Escobar started work on JENKINS-31679 Change By: Emilio Escobar Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clang-scanbuild-plugin] (JENKINS-31679) Remove unnecessary system.err logs
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-31679 Remove unnecessary system.err logs Issue Type: Bug Assignee: Emilio Escobar Components: clang-scanbuild-plugin Created: 20/Nov/15 12:45 PM Priority: Minor Reporter: Emilio Escobar Remove unnecessary system.err logs because the Jenkins log is flooded with errors. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [email-ext-plugin] (JENKINS-31667) Enable customization of attached build log file extension (.txt)
Title: Message Title Alex Earl closed an issue as Won't Do I'd rather not clutter the GUI with even more options at this point. If you really need it, feel free to build a local version of the plugin. Jenkins / JENKINS-31667 Enable customization of attached build log file extension (.txt) Change By: Alex Earl Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Rami Alia created an issue Jenkins / JENKINS-31683 p4-plugin out of memory with large depots on 32 bit java Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 20/Nov/15 3:30 PM Environment: Jenkins 1.634 p4-plugin 1.3.2 Priority: Blocker Reporter: Rami Alia p4 java out of memory exception, stack trace is below. I've worked around this on a couple of slaves by using java64, I'll probably investigate it as well and push up a fix if I track one down but thought I'd pass it on since it adds quite a bit of effort to getting a default jenkins machine master or slave working with decent size depots. stack trace: Nov 20, 2015 10:31:40 AM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask SEVERE: P4 Task: attempt: 1 com.perforce.p4java.exception.ConnectionException: Java heap space at com.perforce.p4java.impl.mapbased.rpc.packet.RpcPacketDispatcher.dispatch(RpcPacketDispatcher.java:225) at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:350) at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:199) at com.perforce.p4java.impl.mapbased.server.Server.execMapCmdList(Server.java:5149) at com.perforce.p4java.impl.mapbased.client.Client.reconcileFiles(Client.java:1593) at
[JIRA] [websphere-deployer-plugin] (JENKINS-31685) failure to upload artifact with custom Keystore and Truststores on websphere
Title: Message Title Rusty Bentz created an issue Jenkins / JENKINS-31685 failure to upload artifact with custom Keystore and Truststores on websphere Issue Type: Bug Assignee: Unassigned Components: websphere-deployer-plugin Created: 20/Nov/15 4:15 PM Environment: Jenkins 1.309, Websphere 8.5.4 ND Labels: websphere-deployer-plugin websphere Priority: Major Reporter: Rusty Bentz When deploying an artifact to Websphere. The application is successfully stopped, but once the artifact tries to upload, the below error occurs: Stopping Old Application 'XX'... Updating 'XX' on IBM WebSphere Application Server Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to updated artifact: Failure uploading archive to server at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.updateArtifact(WebSphereDeploymentService.java:278) at
[JIRA] [envinject-plugin] (JENKINS-31682) Job archive directory is added to the front of the properties file path
Title: Message Title
Cam Spencer updated an issue
Jenkins / JENKINS-31682
Job archive directory is added to the front of the properties file path
Change By:
Cam Spencer
When we try to build another job using a properties file to set the parameters, the directory "C:\Program Files (x86)\Jenkins\jobs\jobName\builds\buildNum\archive\" is added to the front of the specified properties file. This same code was working with Jenkins 1.627, it stopped working after we upgraded to 1.636 . Is this potentially related to https://issues.jenkins-ci.org/browse/JENKINS-23084 ? Injecting Environment Variables{code:java}PROPSFULLFILENAME=${WORKSPACE}\triggeredjobvars.properties{code}Execute Windows Batch Command{code:java}@echo.@echo Creating jobvars.properties file %propsFullFileName%...{code}Console output of the windows batch command {code:java}Creating jobvars.properties file C:\Jenkins\workspace\Audit - All Templates - All Acceptance\triggeredjobvars.properties...{code}After some variables are set in the file, a new job is triggered with the parameters set in the properties file that was created. This is the resulting output:{code:java}ERROR: Build step failed with exceptionjava.nio.file.InvalidPathException: Illegal char <:> at index 95: C:\Program Files (x86)\Jenkins\jobs\Audit - All Templates - All Acceptance\builds\471\archive\C:\Jenkins\workspace\Audit - All Templates - All Acceptance\triggeredjobvars.properties at sun.nio.fs.WindowsPathParser.normalize(Unknown Source) at sun.nio.fs.WindowsPathParser.parse(Unknown Source) at sun.nio.fs.WindowsPathParser.parse(Unknown Source) at sun.nio.fs.WindowsPath.parse(Unknown Source) at sun.nio.fs.WindowsFileSystem.getPath(Unknown Source) at java.io.File.toPath(Unknown Source) at jenkins.util.VirtualFile$FileVF.isIllegalSymlink(VirtualFile.java:301) at jenkins.util.VirtualFile$FileVF.isFile(VirtualFile.java:241) at hudson.plugins.parameterizedtrigger.FileBuildParameters.extractAllValues(FileBuildParameters.java:120) at hudson.plugins.parameterizedtrigger.FileBuildParameters.getAction(FileBuildParameters.java:108) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getBaseActions(BuildTriggerConfig.java:292) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform3(BuildTriggerConfig.java:378) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform3(BlockableBuildTriggerConfig.java:66) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:88) at org.jenkinsci.plugins.conditionalbuildstep.BuilderChain.perform(BuilderChain.java:71) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at
[JIRA] [p4-plugin] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Rami Alia updated an issue Jenkins / JENKINS-31683 p4-plugin out of memory with large depots on 32 bit java Change By: Rami Alia p4 java out of memory exception, stack trace is below. I've worked around this on a couple of slaves by using java64, I'll probably investigate it as well and push up a fix if I track one down but thought I'd pass it on since it adds quite a bit of effort to getting a default jenkins machine master or slave working with decent size depots. last jenkins console output:P4 Task: cleaning workspace to match have list p4 reconcile -w -f -m D:\jenkins\Swarm/... -p4 reconcile -w -f -m D:\jenkins\Swarm/...P4 Task: attempt: 1P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap spaceERROR: P4 Task: failed: com.perforce.p4java.exception.ConnectionException: Java heap spaceArchiving artifactsCreating image galleries.Creating archived images gallery.Recording plot dataFinished: FAILURE stack trace:Nov 20, 2015 10:31:40 AM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTaskSEVERE: P4 Task: attempt: 1com.perforce.p4java.exception.ConnectionException: Java heap spaceat com.perforce.p4java.impl.mapbased.rpc.packet.RpcPacketDispatcher.dispatch(RpcPacketDispatcher.java:225)at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:350)at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:199)at com.perforce.p4java.impl.mapbased.server.Server.execMapCmdList(Server.java:5149)at com.perforce.p4java.impl.mapbased.client.Client.reconcileFiles(Client.java:1593)at org.jenkinsci.plugins.p4.client.ClientHelper.tidyClean(ClientHelper.java:358)at org.jenkinsci.plugins.p4.client.ClientHelper.tidyAutoCleanImpl(ClientHelper.java:285)at org.jenkinsci.plugins.p4.client.ClientHelper.tidyWorkspace(ClientHelper.java:245)at org.jenkinsci.plugins.p4.tasks.CheckoutTask.task(CheckoutTask.java:97)at org.jenkinsci.plugins.p4.tasks.AbstractTask.tryTask(AbstractTask.java:216)at org.jenkinsci.plugins.p4.tasks.CheckoutTask.invoke(CheckoutTask.java:91)at org.jenkinsci.plugins.p4.tasks.CheckoutTask.invoke(CheckoutTask.java:28)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2720)at hudson.remoting.UserRequest.perform(UserRequest.java:121)at hudson.remoting.UserRequest.perform(UserRequest.java:49)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)at java.util.concurrent.FutureTask.run(Unknown Source)at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)at hudson.remoting.Engine$1$1.run(Engine.java:69)at java.lang.Thread.run(Unknown Source)Caused by: java.lang.OutOfMemoryError: Java heap spaceat com.perforce.p4java.impl.mapbased.rpc.func.helper.MD5Digester.digestStream(MD5Digester.java:177)at com.perforce.p4java.impl.mapbased.rpc.func.helper.MD5Digester.digestFileAs32ByteHex(MD5Digester.java:337)at
[JIRA] [promoted-builds-plugin] (JENKINS-8783) Renamin promotion process doesn't remove the original promotion process
Title: Message Title Kyle Estes commented on JENKINS-8783 Re: Renamin promotion process doesn't remove the original promotion process I saw this in v2.19. I thought updating to latest might fix it, but it continues to happen in v2.23.1. Like Michael Peters this is happening for a job in a folder. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-10423) Builds get double promotions after promotion has been renamed
Title: Message Title Kyle Estes edited a comment on JENKINS-10423 Re: Builds get double promotions after promotion has been renamed I saw this in v2.19. I thought updating to latest might fix it, but it continues to happen in v2.23.1. Like [~mpeters] this is happening for a job in a folder. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-31684) timeout when trying to upload an apk to google play probably because of proxy
Title: Message Title Alexander Fendt created an issue Jenkins / JENKINS-31684 timeout when trying to upload an apk to google play probably because of proxy Issue Type: Bug Assignee: Matthew Moore Components: google-oauth-plugin, google-play-android-publisher-plugin Created: 20/Nov/15 4:09 PM Environment: The build job is running on a latest Mac Pro (slave) with all proxies set in jenkins and Mac OS X. Priority: Major Reporter: Alexander Fendt We have issues uploading our apks to google play. We think the applied Proxy settings are not use by the google-oauth-plugin? How can we apply the proxy or is it another issue? Thanks for your help Alex Upload failed: org.jenkinsci.plugins.googleplayandroidpublisher.UploadException: java.security.GeneralSecurityException: Unable to retrieve an access token with the provided credentials at org.jenkinsci.plugins.googleplayandroidpublisher.CredentialsHandler.getServiceAccountCredentials(CredentialsHandler.java:60) at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:301) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30801 Re: Re-triggering a failed build copies the Actions from previous builds Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java http://jenkins-ci.org/commit/build-pipeline-plugin/439eeab2f7060fd542b47c95da1303ec01946ad0 Log: JENKINS-30801 checkstyle fixes Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-22210) On restarting broken build in pipeline, dashboard should update accordingly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22210 Re: On restarting broken build in pipeline, dashboard should update accordingly Code changed in jenkins User: Dan Alvizu Path: pom.xml src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/webapp/js/build-pipeline.js src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/5584922b17cb0e253fe4c9c04677bd3c3995e247 Log: JENKINS-30801 add unit test, update javadoc, remove unused JS Remove 'retryBuild' JS - this is no longer used by any clients, it appears to have been removed in a refactor in JENKINS-22210 . retryBuild functionality would retrigger the build but without any of the upstream cause maintained - it will only work for starting a new pipeline so nothing is really being retried. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30801 Re-triggering a failed build copies the Actions from previous builds Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30801 Re: Re-triggering a failed build copies the Actions from previous builds Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/trigger/BuildPipelineTriggerTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/702b877b7ef9f8b1aa64247b4ad8c215bf76d344 Log: [FIXED JENKINS-30801] Fix missing UpstreamCause UpstreamCause was being removed if it contained a UserIdCause. We really only want to remove the UserIdCause itself, and preserve the rest of the CauseAction to save upstream / downstream relationships. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30801 Re: Re-triggering a failed build copies the Actions from previous builds Code changed in jenkins User: Dan Alvizu Path: pom.xml src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/webapp/js/build-pipeline.js src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/5584922b17cb0e253fe4c9c04677bd3c3995e247 Log: JENKINS-30801 add unit test, update javadoc, remove unused JS Remove 'retryBuild' JS - this is no longer used by any clients, it appears to have been removed in a refactor in JENKINS-22210 . retryBuild functionality would retrigger the build but without any of the upstream cause maintained - it will only work for starting a new pipeline so nothing is really being retried. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30801 Re: Re-triggering a failed build copies the Actions from previous builds Code changed in jenkins User: Dan Alvizu Path: .gitignore src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java http://jenkins-ci.org/commit/build-pipeline-plugin/8357d741b51ada7ad68d810b49871d6ff21b1bea Log: JENKINS-30801 limit Action objects in re-trigger to CauseAction Passing all Action objects from previous builds results in unexpected behavior: certain publisher and Builder rely on them to publish information about the build, and should not be copied to the next build. The only reason to copy Action objects is to preserve the cause of the build in order to keep it in the pipeline and replay how the build was triggered. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-20792) since 1.3.4 we can't use remote api to create pipeline
Title: Message Title Dan Alvizu closed an issue as Won't Fix This is an internal API and is not supported. For building pipelines from code, please consider using the job-dsl plugin: https://github.com/jenkinsci/job-dsl-plugin Jenkins / JENKINS-20792 since 1.3.4 we can't use remote api to create pipeline Change By: Dan Alvizu Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-28784) JUnitResultArchiver testDataPublishers not compatible with Workflow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28784 JUnitResultArchiver testDataPublishers not compatible with Workflow Change By: Jesse Glick Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-31686) Jenkins injects the old git commit as GIT_COMMIT env variable
Title: Message Title Kowal Cj0 created an issue Jenkins / JENKINS-31686 Jenkins injects the old git commit as GIT_COMMIT env variable Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 20/Nov/15 4:18 PM Environment: Jenkins v1.638 Oracle Java 1.8.0_66 Ubuntu 3.13.0-48-generic x86_64 Labels: git git-client Priority: Major Reporter: Kowal Cj0 Compare GIT_COMMIT, GIT_PREVIOUS_COMMIT with ghprbActualCommit GitHub pull request #21 of commit 91cdd0e62caf929448a09caf57df9f99bc7dafd6, no merge conflicts. GitHub pull request #21 of commit 91cdd0e62caf929448a09caf57df9f99bc7dafd6, no merge conflicts. Setting status of 91cdd0e62caf929448a09caf57df9f99bc7dafd6 to PENDING with url http://jenkins.net:8080/job/build-on-PR/82/ and message: 'Build started sha1 is merged.' [EnvInject] - Loading node environment variables. Building on master in workspace /var/lib/jenkins/workspace/build-on-PR [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Done Cloning the remote Git repository Cloning
[JIRA] [build-pipeline-plugin] (JENKINS-24883) Artifacts not found on re-runs of manual jobs in pipeline
Title: Message Title Dan Alvizu resolved as Fixed Jenkins / JENKINS-24883 Artifacts not found on re-runs of manual jobs in pipeline Change By: Dan Alvizu Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-30581) user input in build pipeline step breaks the pipeline
Title: Message Title Dan Alvizu closed an issue as Cannot Reproduce +1 to Ioannis Moutsatsos - it's not clear to me what the issue is. Please include steps to reproduce and expected / observed behavior. There was a known issue in the build pipeline 1.4.8 with fancybox not working with jquery 1.1x - specifically an issue working with the extensible-choice-parameter plugin, which it sounds like you used. That's been fixed in master and will be in the 1.4.9 release. Since there's no feedback on this issue yet I'm going to close it out. Please re-open if you see the behavior again and provide steps to reproduce. Thanks! Jenkins / JENKINS-30581 user input in build pipeline step breaks the pipeline Change By: Dan Alvizu Status: Open Closed Assignee: Bruno P. Kinoshita stephen newman Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30023 Re: OWASP Dependency-Check Plugin does not respect supressions anymore Code changed in jenkins User: Steve Springett Path: src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyCheckBuilder.java http://jenkins-ci.org/commit/dependency-check-plugin/78e16bde14230a1daf064b954d08d653fb1cdad5 Log: Added variable substitution back to URLs. JENKINS-30023 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-30023) OWASP Dependency-Check Plugin does not respect supressions anymore
Title: Message Title Steve Springett commented on JENKINS-30023 Re: OWASP Dependency-Check Plugin does not respect supressions anymore Good catch Victor Noël. The substitution code has been added back in for URLs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-10423) Builds get double promotions after promotion has been renamed
Title: Message Title Kyle Estes commented on JENKINS-10423 Re: Builds get double promotions after promotion has been renamed I saw this in v2.19. I thought updating to latest might fix it, but it continues to happen in v2.23.1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30801 Re: Re-triggering a failed build copies the Actions from previous builds Code changed in jenkins User: Dan Alvizu Path: .gitignore pom.xml src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/webapp/js/build-pipeline.js src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/trigger/BuildPipelineTriggerTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/c05598dfef7dc2258e111e64de2a470e1df6d98f Log: Merge pull request #89 from dalvizu/ JENKINS-30801 -2 [Fixed JENKINS-30801] Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/11ce036fb7fa...c05598dfef7d Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-31120) blank page show up after click run button with parameterized builds
Title: Message Title Dan Alvizu assigned an issue to Dan Alvizu Jenkins / JENKINS-31120 blank page show up after click run button with parameterized builds Change By: Dan Alvizu Assignee: Dan Alvizu Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31654) Jobs of MultiJob type are not created while jenkins report success
Title: Message Title Daniel Spilker commented on JENKINS-31654 Re: Jobs of MultiJob type are not created while jenkins report success I can not reproduce this on 1.609.2. Are there any exceptions in your Jenkins log? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31653) readFileFromWorkspace doesn't not update the shell step if the referenced file content has changed
Title: Message Title
Daniel Spilker commented on JENKINS-31653
Re: readFileFromWorkspace doesn't not update the shell step if the referenced file content has changed
I can't reproduce this with this script:
job('example') {
steps {
shell(readFileFromWorkspace("/tmp/myscript.sh"))
}
}
Your example seems to have a typo, it's steps and not step.
Note that the file will be read on the node which is running the seed job, which may or may not be the master node. Did you update the file on the correct node?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [deployment-notification-plugin] (JENKINS-28632) Workflow support for Deployment Notification trigger
Title: Message Title Jesse Glick commented on JENKINS-28632 Re: Workflow support for Deployment Notification trigger what would happen if the deployment send the finish event notification before awaitDeployment started to listen for it? IIUC Jenkins is already listening for the event notification and so it should have received the event. So the step would need to somehow determine when it starts that the event has already been received. But yes a block-scoped step would probably make this easier to do. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31585) worflow editor cannot be expanded any more
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31585 Re: worflow editor cannot be expanded any more Code changed in jenkins User: tfennelly Path: cps/gulpfile.js cps/package.json cps/src/main/js/samples.js cps/src/main/js/workflow-editor.js http://jenkins-ci.org/commit/workflow-plugin/84146c34f8d6f2206382c76e62d8d3a240bfb2a7 Log: [Fixed JENKINS-31585] Make workflow editor (ACE) resizable. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31585) worflow editor cannot be expanded any more
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31585 Re: worflow editor cannot be expanded any more Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/gulpfile.js cps/package.json cps/src/main/js/samples.js cps/src/main/js/workflow-editor.js http://jenkins-ci.org/commit/workflow-plugin/70629b4b6398843dd309fdaa8f1daf07c818e594 Log: [FIXED JENKINS-31585] Noting merge of #255. Compare: https://github.com/jenkinsci/workflow-plugin/compare/3360b00a24f4...70629b4b6398 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-24883) Artifacts not found on re-runs of manual jobs in pipeline
Title: Message Title Dan Alvizu commented on JENKINS-24883 Re: Artifacts not found on re-runs of manual jobs in pipeline Merged to master will be in 1.4.9 release Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-20792) since 1.3.4 we can't use remote api to create pipeline
Title: Message Title Dan Alvizu stopped work on JENKINS-20792 Change By: Dan Alvizu Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31604) UserCause does not get set properly by DSL plugin for conditional run steps.
Title: Message Title Daniel Spilker commented on JENKINS-31604 Re: UserCause does not get set properly by DSL plugin for conditional run steps. pull request: https://github.com/jenkinsci/job-dsl-plugin/pull/669 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Rusty Bentz updated an issue Jenkins / JENKINS-30250 StackOverflowError in Websphere Deployer Change By: Rusty Bentz Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31585) worflow editor cannot be expanded any more
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31585 worflow editor cannot be expanded any more Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30801 Re: Re-triggering a failed build copies the Actions from previous builds Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/fb49ded545db776497cd0692d0032cad40ff3fab Log: JENKINS-30801 fix ConcurrentModificationException, add test Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30801) Re-triggering a failed build copies the Actions from previous builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30801 Re: Re-triggering a failed build copies the Actions from previous builds Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineViewTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/13fa2c972bbd156460e5515b3e23b1445cd907bb Log: JENKINS-30801 Copy over ParametersAction as well Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-31688) jenkins safe-restart hanging forever when waiting for locking a ssh-slave connection for unregistration without timeout
Title: Message Title
Ellen shen created an issue
Jenkins / JENKINS-31688
jenkins safe-restart hanging forever when waiting for locking a ssh-slave connection for unregistration without timeout
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
remoting, ssh-slaves-plugin
Created:
20/Nov/15 5:00 PM
Priority:
Blocker
Reporter:
Ellen shen
safe-restart is waiting to close a registered connection. but that connection is waiting for being notified forever while the notifier thread either dead or hanging. there is no timeout in wait. so safe-restart hanging forever.
our environment is jenkins 1.538 and ssh-slave plugin 1.9 but seems the issue i described still hold true in latest code base. https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/src/main/java/hudson/plugins/sshslaves/PluginImpl.java /**
Closes all the registered connections. */ private static synchronized void closeRegisteredConnections() { for (Connection connection : activeConnections)
Unknown macro: { LOGGER.log(Level.INFO, "Forcing connection to {0}}
activeConnections.clear(); }
https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/channel/ChannelManager.java private
[JIRA] [junit-plugin] (JENKINS-28784) JUnitResultArchiver testDataPublishers not compatible with Workflow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28784 JUnitResultArchiver testDataPublishers not compatible with Workflow Change By: Jesse Glick Component/s: junit-plugin Component/s: workflow-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31687) Which node Groovy code actually executes on is not documented clearly
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-31687
Which node Groovy code actually executes on is not documented clearly
Issue Type:
Bug
Assignee:
Jesse Glick
Attachments:
workflow-tooltip.png
Components:
workflow-plugin
Created:
20/Nov/15 4:44 PM
Environment:
workflow-plugin 1.11
Priority:
Minor
Reporter:
R. Tyler Croy
The documentation in the tooltip informs the user that they are able to use the Groovy GDK but doesn't make it clear to the user on which machine the Groovy code will execute.
James Nord mentioned with the following snippet that it wouldn't work because it would run on the master:
node {
if (System.getProperty("os.name") == 'Linux') {
sh 'echo "hi"'
}
}
[JIRA] [build-pipeline-plugin] (JENKINS-31120) blank page show up after click run button with parameterized builds
Title: Message Title Dan Alvizu commented on JENKINS-31120 Re: blank page show up after click run button with parameterized builds Related fix here, can't reproduce the issue described after this fix: https://github.com/jenkinsci/build-pipeline-plugin/pull/78 Will be in 1.4.9 release. Can you build / deploy from master and see if this fixes your issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30917) "manual trigger" can't be disable
Title: Message Title Dan Alvizu closed an issue as Won't Do Jenkins / JENKINS-30917 "manual trigger" can't be disable Change By: Dan Alvizu Status: Reopened Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30917) "manual trigger" can't be disable
Title: Message Title Dan Alvizu reopened an issue Jenkins / JENKINS-30917 "manual trigger" can't be disable Change By: Dan Alvizu Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-21422) Jenkins crashing due to out of memory when rebuilding jobs
Title: Message Title Dan Alvizu assigned an issue to Dan Alvizu Jenkins / JENKINS-21422 Jenkins crashing due to out of memory when rebuilding jobs Change By: Dan Alvizu Assignee: Dan Alvizu Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-14591) Add the ability to choose which parameters build will be displayed
Title: Message Title Dan Alvizu commented on JENKINS-14591 Re: Add the ability to choose which parameters build will be displayed Related PR here: https://github.com/jenkinsci/build-pipeline-plugin/pull/74 This would be nice to pull into a strategy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-14228) clock.png icon not displayed in build pipeline
Title: Message Title Dan Alvizu resolved as Cannot Reproduce Can't reproduce in latest. Reopen if still an issue Jenkins / JENKINS-14228 clock.png icon not displayed in build pipeline Change By: Dan Alvizu Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter-plugin] (JENKINS-31690) getGroovyBinding NPE
Title: Message Title jim gedarovich created an issue Jenkins / JENKINS-31690 getGroovyBinding NPE Issue Type: Bug Assignee: vimil Components: extended-choice-parameter-plugin Created: 20/Nov/15 5:43 PM Priority: Blocker Reporter: jim gedarovich JENKINS VERSION: 1.625.2 LTE PLUGIN VERSION: 0.53 when a job is triggered that uses the "Choose Source for Default Value" and the "Default Groovy Script" option is used, an NPE is generated when the job is run. Nov 20, 2015 4:25:00 PM com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition executeGroovyScriptAndProcessGroovyValue SEVERE: null java.lang.NullPointerException at com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition.getGroovyBinding(ExtendedChoiceParameterDefinition.java:690) at com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition.getGroovyShell(ExtendedChoiceParameterDefinition.java:711) at com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition.executeGroovyScript(ExtendedChoiceParameterDefinition.java:671) at com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition.executeGroovyScriptAndProcessGroovyValue(ExtendedChoiceParameterDefinition.java:660) at com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition.computeValue(ExtendedChoiceParameterDefinition.java:633) at
[JIRA] [github-sqs-plugin] (JENKINS-24839) GitHub Repository on Save project Config
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-24839 GitHub Repository on Save project Config Change By: Kanstantsin Shautsou Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31689) new (ACE) workflow editor shows above the Apply Button.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31689 new (ACE) workflow editor shows above the Apply Button. Change By: Jesse Glick Labels: regression user-experience Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25430) Clicking on "console" icon doesn't work
Title: Message Title Dan Alvizu resolved as Fixed Jenkins / JENKINS-25430 Clicking on "console" icon doesn't work Change By: Dan Alvizu Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipeline Plugin no longer allows starting build with parameters
Title: Message Title Dan Alvizu closed an issue as Duplicate Fixed in JENKINS-25430 , tracking there. Fixed in master, will be fixed in next release (1.4.9) Jenkins / JENKINS-25427 Build Pipeline Plugin no longer allows starting build with parameters Change By: Dan Alvizu Status: In Progress Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31689) new (ACE) workflow editor shows above the Apply Button.
Title: Message Title James Nord created an issue Jenkins / JENKINS-31689 new (ACE) workflow editor shows above the Apply Button. Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 20/Nov/15 5:17 PM Environment: workfow 1.11 Labels: UI Priority: Minor Reporter: James Nord When you scroll a workflow configuration the Apply button can get partially obscured by the ACE editor. The ACE editor should get shaded out and be behind the save / apply buttons just like the rest of the configuration.
[JIRA] [workflow-plugin] (JENKINS-31689) new (ACE) workflow editor shows above the Apply Button.
Title: Message Title Tom FENNELLY assigned an issue to Tom FENNELLY Jenkins / JENKINS-31689 new (ACE) workflow editor shows above the Apply Button. Change By: Tom FENNELLY Assignee: Jesse Glick Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-29620) Incompatible with latest jQuery plugin
Title: Message Title Dan Alvizu closed an issue as Duplicate Duplicate of JENKINS-25430 Jenkins / JENKINS-29620 Incompatible with latest jQuery plugin Change By: Dan Alvizu Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31689) new (ACE) workflow editor shows above the Apply Button.
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-31689 new (ACE) workflow editor shows above the Apply Button. Change By: Tom FENNELLY Labels: UI user-experience Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31689) new (ACE) workflow editor shows above the Apply Button.
Title: Message Title Tom FENNELLY commented on JENKINS-31689 Re: new (ACE) workflow editor shows above the Apply Button. The buttons are the real problem here. Those floating buttons make me want to vomit. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
