[JIRA] (JENKINS-37581) Allow using environment variables for clientID and clientSecret
Title: Message Title
Esko Suomi created an issue
Jenkins / JENKINS-37581
Allow using environment variables for clientID and clientSecret
Issue Type:
New Feature
Assignee:
Sam Gleske
Components:
github-oauth-plugin
Created:
2016/Aug/22 7:09 AM
Environment:
Dockerized Jenkins 2.7.2+ with github-oauth:0.24
Priority:
Major
Reporter:
Esko Suomi
As title says, I would like to be able to use environment variables (for example ${GITHUB_OAUTH_CLIENTID}, ${GITHUB_OAUTH_CLIENTSECRET}) for configuring the GitHub OAuth application parameters. This would allow me to keep all secrets away from configuration files and instead keep them in environment variables where they can be managed more securely and effectively. For a bit more context, I've built a custom Dockerfile on top of the official Jenkins Docker image which includes useful configuration from a set of template files and as such, this of course includes the GitHub OAuth plugin's configuration which happens to live in config.xml's definition. Security wise it does not make any sense at all to bake in passwords to a Docker image and as this particular plugin does not support environment variables, I had to add a hack around the /usr/local/bin/jenkins.sh which uses sed to rewrite the config file just before Jenkins is actually started. As an additional note, enabling env variables would also bring the plugin closer to how eg. and are configured. I also suspect there's a plethora of other plugins which would benefit from such unified behaviour but that would be a whole another effort to "encourage" all plugins to support password injection from environment variables.
[JIRA] (JENKINS-37542) Jenkins is not scheduling jobs for offline nodes
Title: Message Title Giuseppe Landolfi commented on JENKINS-37542 Re: Jenkins is not scheduling jobs for offline nodes Not 100% sure, but I believe you are right: It seems that the Git plugin - which I understand you use for SCM polling - needs the slave to be up for doing the polling. Note that this behavior doesn't come from Jenkins core, but rather from the Git plugin. Other plugins such as the Subversion plugin don't have this limitation. The good news is that the Git plugin also supports polling from the master (see documentation, section "Fast Remote Polling"), and the feature should be enabled by default on recent versions of the plugin (such as yours). Clearly it's not working for you, and the doc linked above suggests that this may happen if you don't have a working Git installation on the master node, and in such case the legacy poll from the slave is used as fallback behavior. To move forward I would suggest you the following solutions - ordered from the best to the worst, but still solutions: try to make the fast remote polling work by checking what's wrong (best candidate would be git installation on the master node) if that doesn't work, consider converting your job to a pipleline job: in the pipeline you can do two checkouts: one on the master node, and use it for polling, and one on the slave and use it for all the stuff you need (except polling) if you don't like the above, you can disable the polling on your job, and create an upstream job, that runs on master and only has a checkout from the git repo: this way, the upstream job will be polling from master, and whenever a build is trigger, its execution will result in the trigger of the downstream job > Let me know if this works for you. For what regards this item, I would consider this as "intended behavior", the limitation being in the Git plugin rather than in the Slave Setup plugin itself. On the other hand, this is a scenario that is more than worth mentioning in the documentation of the Slave Setup plugin as it's going to be a common issue. > What do you think? Add Comment
[JIRA] (JENKINS-15376) Extraordinary memory use associated with svn plugin
Title: Message Title Emil Styrke commented on JENKINS-15376 Re: Extraordinary memory use associated with svn plugin This affects us too. Apparently, there is a pull request available at https://github.com/jenkinsci/subversion-plugin/pull/166, and I have confirmed that this fixes the issue for us. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37582) Stacktrace when creating Users/Group
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-37582 Stacktrace when creating Users/Group Change By: Allan BURDAJEWICZ Summary: Stacktrace when creating Users/Group with cache enabled Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37582) Stacktrace when creating Users/Group with cache enabled
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-37582 Stacktrace when creating Users/Group with cache enabled Issue Type: Improvement Assignee: Félix Belzunce Arcos Attachments: error-with-project-auth.png, error-with-rbac.png Components: active-directory-plugin Created: 2016/Aug/22 7:58 AM Environment: active-directory-plugin:1.47 Jenkins:1.651 Priority: Major Reporter: Allan BURDAJEWICZ (Note: This does not prevent from creating a Group/User but not sure of the impact on the cache mechanism) Whenever I tried to create a Group/User, Active Directory throws a stacktrace: com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key support. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.loadGroupByGroupname(ActiveDirectoryUnixAuthenticationProvider.java:367) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadGro
[JIRA] (JENKINS-37582) Stacktrace when creating Users/Group
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-37582
Stacktrace when creating Users/Group
Change By:
Allan BURDAJEWICZ
(Note: This does not prevent from creating a Group/User but not sure of the impact on the cache mechanism)h3. Whenever I tried to create a Group/User, Active Directory throws a stacktrace:{code}com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key support. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.loadGroupByGroupname(ActiveDirectoryUnixAuthenticationProvider.java:367) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadGroupByGroupname(ActiveDirectorySecurityRealm.java:720) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:351) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:314) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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 com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:35) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter
[JIRA] (JENKINS-37550) Error al visualizar pantalla configuración proyectos
Title: Message Title Rebeca Perez updated an issue Jenkins / JENKINS-37550 Error al visualizar pantalla configuración proyectos Change By: Rebeca Perez Attachment: jenkins.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34407) junit-plugin parse error
Title: Message Title George Fischhof reopened an issue I have the same issue with JUnit plugin version 1.18, Jenkins 2.18, on windows 8.1 x64, JAVA_VERSION="1.8.0_91" stack trace: at hudson.tasks.junit.TestResult.parse(TestResult.java:306) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:244) at hudson.tasks.junit.TestResult.parse(TestResult.java:175) at hudson.tasks.junit.TestResult.parse(TestResult.java:154) at hudson.tasks.junit.TestResult.(TestResult.java:126) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:132) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:107) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:103) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:128) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:149) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: java.lang.NullPointerException at hudson.tasks.junit.CaseResult.(CaseResult.java:116) at hudson.tasks.junit.SuiteResult.(SuiteResult.java:200) at hudson.tasks.junit.SuiteResult.parseSuite(SuiteResult.java:144) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129) at hudson.tasks.junit.TestResult.parse(TestResult.java:301) ... 21 more Jenkins / JENKINS-34407 junit-plugin parse error Change By: George Fischhof Resolution: Fixed Status: Resolved Reopened
[JIRA] (JENKINS-37582) Stacktrace when creating Users/Group
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-37582
Stacktrace when creating Users/Group
Change By:
Allan BURDAJEWICZ
(Note: This does not prevent from creating a Group/User but not sure of the impact on the cache mechanism)h3. Issue Whenever I tried to create a Group/User, Active Directory throws a stacktrace . The same happens with different Authorization strategy. Tested with Cloudbees RBAC (see [^error-with-rbac.png]) and Matrix Authorization (see [^error-with-project-auth.png])h4. Stacktrace for Matrix Auth :{code}com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key support. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.loadGroupByGroupname(ActiveDirectoryUnixAuthenticationProvider.java:367) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadGroupByGroupname(ActiveDirectorySecurityRealm.java:720) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:351) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:314) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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 com.cloudbees.jenkins.h
[JIRA] (JENKINS-34407) junit-plugin parse error
Title: Message Title Oliver Gondža commented on JENKINS-34407 Re: junit-plugin parse error George Fischhof, That stacktrace is unrelated to this issue. Please file a separate one if it is not already. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36641) End to end test acceptance tests for personalization
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36641 End to end test acceptance tests for personalization Change By: James Dumay Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37544) Regression storybook support for dashboard is broken
Title: Message Title Michael Neale commented on JENKINS-37544 Re: Regression storybook support for dashboard is broken Is this one blocking Thorsten Scherler? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30622) Add View Mask Polling Filter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30622 Re: Add View Mask Polling Filter Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/filters/FilterViewMaskImpl.java src/main/java/org/jenkinsci/plugins/p4/tasks/PollTask.java src/main/resources/org/jenkinsci/plugins/p4/filters/FilterViewMaskImpl/config.jelly src/main/resources/org/jenkinsci/plugins/p4/filters/FilterViewMaskImpl/help-viewMask.html src/test/java/org/jenkinsci/plugins/p4/client/ConnectionTest.java http://jenkins-ci.org/commit/p4-plugin/a4b9b3a00983586f41da8fd0da685902d307c1f9 Log: (@stuartr) Implementing View Mask Filter. JENKINS-30622 JENKINS-28225 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28225) Add include filters for build trigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28225 Re: Add include filters for build trigger Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/filters/FilterViewMaskImpl.java src/main/java/org/jenkinsci/plugins/p4/tasks/PollTask.java src/main/resources/org/jenkinsci/plugins/p4/filters/FilterViewMaskImpl/config.jelly src/main/resources/org/jenkinsci/plugins/p4/filters/FilterViewMaskImpl/help-viewMask.html src/test/java/org/jenkinsci/plugins/p4/client/ConnectionTest.java http://jenkins-ci.org/commit/p4-plugin/a4b9b3a00983586f41da8fd0da685902d307c1f9 Log: (@stuartr) Implementing View Mask Filter. JENKINS-30622 JENKINS-28225 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30622) Add View Mask Polling Filter
Title: Message Title Paul Allen resolved as Fixed Ready for release Jenkins / JENKINS-30622 Add View Mask Polling Filter Change By: Paul Allen Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28225) Add include filters for build trigger
Title: Message Title Paul Allen resolved as Fixed Ready for release Jenkins / JENKINS-28225 Add include filters for build trigger Change By: Paul Allen Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37476) SSL string not added to p4port (parallel sync)
Title: Message Title Paul Allen resolved as Fixed Ready for release Jenkins / JENKINS-37476 SSL string not added to p4port (parallel sync) Change By: Paul Allen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33046) Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs
Title: Message Title Anna Tikhonova commented on JENKINS-33046 Re: Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs Alexander Komarov Yep I couldn't agree more that it's absolutely unnecessary to set custom build numbers on feature/bugfix/hotfix jobs, but what about release branches? How should they be managed by design in Multibranch pipeline projects? Could you please suggest/shed some light on the intended workflow for them? The whole multibranch pipeline feature is super hot and we'd absolutely love to switch to it entirely, but still we'd like to keep the build number part of our workflow. Let me describe what it's like and why we want it. Assume our current master build number is N. We branch each release out of master and bump master build numbers to N + M, where M is a "window" that should be enough for this release branch lifetime. We do not build releases on each commit but every 4 hours, which makes it easy to make a fine estimate for M. This scheme makes build comparison straight-forward, by their build numbers. We can track where the branching has happened and determine where in commit history the particular build belongs (approx.) just by looking at its build number. Convenient because you can see if a patch was included into that particular build. Also, as Bryden Oliver has mentioned, build numbers might be visible to customers (which is true in our case as well, but we don't set them to something like '43p1'; we just bump the standard numerical build numbers in Jenkins), so I suppose many would like an opportunity to control them. Please, for the sake of never failing build, help. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37583) Configurable ssh port for packaging scripts breaks publishing ig default options are used
Title: Message Title Armando Fernandez created an issue Jenkins / JENKINS-37583 Configurable ssh port for packaging scripts breaks publishing ig default options are used Issue Type: Bug Assignee: Armando Fernandez Components: packaging Created: 2016/Aug/22 9:03 AM Priority: Minor Reporter: Armando Fernandez Default value for SSH port causes the publishing to fail since it includes unneeded double quotes in command to execute: rsync -avz -e "ssh "-p 22"" ... Note double quotes in "-p 22". Command to execute should be: rsync -avz -e "ssh -p 22" ... Add Comment
[JIRA] (JENKINS-37583) Configurable ssh port for packaging scripts breaks publishing ig default options are used
Title: Message Title Armando Fernandez started work on JENKINS-37583 Change By: Armando Fernandez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30019) It does not work with Jenkins Workflow jobs
Title: Message Title Anna Tikhonova commented on JENKINS-30019 Re: It does not work with Jenkins Workflow jobs +1 for Multibranch Pipeline support! Prevents us from switching to multibranch pipelines completely. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34407) junit-plugin parse error
Title: Message Title George Fischhof assigned an issue to George Fischhof The error was my mistake: accidentally I put an attribute to node in the xml file. When I fixed the xml, the parsing was good Sorry guys. Jenkins / JENKINS-34407 junit-plugin parse error Change By: George Fischhof Assignee: George Fischhof Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34407) junit-plugin parse error
Title: Message Title George Fischhof assigned an issue to Unassigned please close this issue, it is good in 1.18 Jenkins / JENKINS-34407 junit-plugin parse error Change By: George Fischhof Assignee: George Fischhof Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34407) junit-plugin parse error
Title: Message Title George Fischhof resolved as Fixed the issue I reported against 1.18 was my mistake (I used a wrong xml file) Jenkins / JENKINS-34407 junit-plugin parse error Change By: George Fischhof Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Mayur Barge commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Hi Jesse Glick Greetings ! Are there any plans to get GitPublisher working soon ? OR to fix the special characters issue mentioned by Russell Gallop Thanks Russell Gallop for the workaround. But as you mentioned it shows password in the console output. Any other suggestions ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37544) Regression storybook support for dashboard is broken
Title: Message Title Thorsten Scherler commented on JENKINS-37544 Re: Regression storybook support for dashboard is broken Well it removes the possibilities to create quickly new components. Not directly ATM but it is a blocker, since it is a Regression Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title BBVA commented on JENKINS-19445 Re: Jobs randomly stuck with "building remotely on slave-name" message Dave Taddei, can you confirm you are using the property hudson.remoting.RemoteClassLoader.force to force the load of com.sun.jna.Native. Also that you can see that the class is being loaded via the log of the slave. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37544) Regression storybook support for dashboard is broken
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37544 Regression storybook support for dashboard is broken Change By: Michael Neale Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37544) Regression storybook support for dashboard is broken
Title: Message Title Michael Neale commented on JENKINS-37544 Re: Regression storybook support for dashboard is broken Thorsten Scherler I might make it critical, realistically I don't think keith will get to look at this for a while. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37528) JiraTestResultReporter-plugin needs TestNG support
Title: Message Title Catalin Luta updated an issue Jenkins / JENKINS-37528 JiraTestResultReporter-plugin needs TestNG support Change By: Catalin Luta Issue Type: Bug New Feature Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title
squalou jenkins created an issue
Jenkins / JENKINS-37584
P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2016/Aug/22 10:14 AM
Environment:
jenkins 2.7.2 LTS p4-plgin 1.3.8 jdk 1.8 (sun) OS : redhat 7.2
Priority:
Major
Reporter:
squalou jenkins
I'm using p4 plugin for several months in freestyle jobs, and I'm moving to 'pipelines' implementation (workflow if you like) According to this documentation, there are some known limitations : https://github.com/jenkinsci/pipeline-plugin/blob/master/README.md especially :
No access to Environment ${VAR} variables
On the other hand, one line below is written : Exposed Variables :
P4_CHANGELIST - current changelist (valid for this to be blank when there are no changes).
Within my pipelines, what I see is that 'P4_CHANGELIST' is not available after a call to p4sync. Is it expected ? If so, how do I retrieve the changelist at which the sync is done ? (in order to propagate it to further steps and stages in the pipeline)
[JIRA] (JENKINS-37281) Remove "StopPropagation" from blueocean-dashboard module
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37281 Remove "StopPropagation" from blueocean-dashboard module Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37281) Remove "StopPropagation" from blueocean-dashboard module
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37281 Remove "StopPropagation" from blueocean-dashboard module Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36895) favorite star layout issues if running at page zoom < 100%
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36895 favorite star layout issues if running at page zoom < 100% Change By: James Dumay Sprint: 1.0-m12, 1.0-pre-beta-1 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36895) favorite star layout issues if running at page zoom < 100%
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36895 favorite star layout issues if running at page zoom < 100% Change By: James Dumay Sprint: 1.0-m12, 1.0-pre-beta-1 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37585) Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Title: Message Title
Raul Arabaolaza created an issue
Jenkins / JENKINS-37585
Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Issue Type:
Improvement
Assignee:
Raul Arabaolaza
Components:
plugin-compat-tester
Created:
2016/Aug/22 10:50 AM
Priority:
Minor
Reporter:
Raul Arabaolaza
The PCT can not be run against jenkins versions that embed a RC, alpha or beta version of ```jenkins-core```, trying to do that results in: ``` Exception in thread "main" java.io.IOException: no jenkins-core.jar in jenkins.war at org.jenkins.tools.test.PluginCompatTester.scanWAR(PluginCompatTester.java:517) at org.jenkins.tools.test.PluginCompatTester.testPlugins(PluginCompatTester.java:158) at org.jenkins.tools.test.PluginCompatTesterCli.main(PluginCompatTesterCli.java:110) ``` The reason is that the method scanWar in PluginCompatTester uses the following code to locate the jenkins-core war
Matcher m = Pattern.compile("WEB-INF/lib/jenkins-core-([0-9.]+(?:-[0-9.]+)?(?:-SNAPSHOT)?)[.]jar").matcher(name);
[JIRA] (JENKINS-37585) Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Title: Message Title
Raul Arabaolaza updated an issue
Jenkins / JENKINS-37585
Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Change By:
Raul Arabaolaza
The PCT can not be run against jenkins versions that embed a RC _RC_ , alpha _alpha_ or beta _beta_ version of ``` {{ jenkins-core ``` }} , trying to do that results in: ``` {code} Exception in thread "main" java.io.IOException: no jenkins-core.jar in jenkins.war at org.jenkins.tools.test.PluginCompatTester.scanWAR(PluginCompatTester.java:517) at org.jenkins.tools.test.PluginCompatTester.testPlugins(PluginCompatTester.java:158) at org.jenkins.tools.test.PluginCompatTesterCli.main(PluginCompatTesterCli.java:110) ```The reason is that the method scanWar in PluginCompatTester uses the following code to locate the {{ jenkins-core }} war{code:java}Matcher m = Pattern.compile("WEB-INF/lib/jenkins-core-([0-9.]+(?:-[0-9.]+)?(?:-SNAPSHOT)?)[.]jar").matcher(name);{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37585) Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Title: Message Title
Raul Arabaolaza updated an issue
Jenkins / JENKINS-37585
Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Change By:
Raul Arabaolaza
The PCT can not be run against jenkins versions that embed a _RC_, _alpha_ or _beta_ version of {{jenkins-core}}, trying to do that results in:{code}Exception in thread "main" java.io.IOException: no jenkins-core.jar in jenkins.war at org.jenkins.tools.test.PluginCompatTester.scanWAR(PluginCompatTester.java:517) at org.jenkins.tools.test.PluginCompatTester.testPlugins(PluginCompatTester.java:158) at org.jenkins.tools.test.PluginCompatTesterCli.main(PluginCompatTesterCli.java:110) ``` {code} The reason is that the method scanWar in PluginCompatTester uses the following code to locate the {{jenkins-core}} war{code:java}Matcher m = Pattern.compile("WEB-INF/lib/jenkins-core-([0-9.]+(?:-[0-9.]+)?(?:-SNAPSHOT)?)[.]jar").matcher(name);{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received
[JIRA] (JENKINS-37586) WORKSPACE environment variable not available in Jenkins pipeline
Title: Message Title Jean Baptiste Favre created an issue Jenkins / JENKINS-37586 WORKSPACE environment variable not available in Jenkins pipeline Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/22 11:00 AM Environment: Debian Jessie Jenkins 2.7.2, one master + 2 SSH slaves Pipeline plugin 2.2 Priority: Major Reporter: Jean Baptiste Favre Since the upgrade to Jenkins 2.7.2 & pipeline plugin 2.2, WORKSPACE is not available anymore in my groovy pipeline script. Issue looks like https://issues.jenkins-ci.org/browse/JENKINS-36545 but since I'm a Jenkins newbie, I can't confirm they're the same. Since shell scripts launched by pipeline use this variable, I basically can't use it anymore. Jenkins is started with following options: -Djava.awt.headless=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpListenAddress=127.0.0.1 --httpPort=$HTTP_PORT --ajp13Port=$AJP_PORT -Dhudson.model.ParametersAction.keepUndefinedParameters=true I first though it was somewhat related to https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11. I tried to use default options -Djava.awt.headless=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080
[JIRA] (JENKINS-36054) Reload page after hibernate
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36054 Reload page after hibernate Change By: James Dumay Sprint: 1.0-japan-m9, 1.0-m10, 1.0-m11, 1.0-m12, 1.0-pre-beta-1 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36054) Reload page after hibernate
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36054 Reload page after hibernate Change By: James Dumay Sprint: 1.0-japan-m9, 1.0-m10, 1.0-m11, 1.0-m12, 1.0-pre-beta-1 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35153) Events.JobChannel#job_crud_deleted publishing blocked by AccessControl
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35153 Events.JobChannel#job_crud_deleted publishing blocked by AccessControl Change By: James Dumay Sprint: 1.0-japan-m9, 1.0-m11, 1.0-m12, 1.0-pre-beta-1 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35153) Events.JobChannel#job_crud_deleted publishing blocked by AccessControl
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35153 Events.JobChannel#job_crud_deleted publishing blocked by AccessControl Change By: James Dumay Sprint: 1.0-japan-m9, 1.0-m11, 1.0-m12, 1.0-pre-beta-1 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37244) Consistent terminology for builds / pipeline runs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37244 Consistent terminology for builds / pipeline runs Change By: James Dumay Sprint: 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37166) Update the styling of the test result content
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37166 Update the styling of the test result content Change By: James Dumay Sprint: 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35810) Developer sees the Branches tab organised by relevance
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35810 Developer sees the Branches tab organised by relevance Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37166) Update the styling of the test result content
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37166 Update the styling of the test result content Change By: James Dumay Sprint: 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35810) Developer sees the Branches tab organised by relevance
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35810 Developer sees the Branches tab organised by relevance Change By: James Dumay Sprint: 1.0-pre-beta-1 , 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37244) Consistent terminology for builds / pipeline runs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37244 Consistent terminology for builds / pipeline runs Change By: James Dumay Sprint: 1.0-beta-1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37585) Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Title: Message Title Raul Arabaolaza started work on JENKINS-37585 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37423) Connection refused when trying to release
Title: Message Title Yogesh Lonkar commented on JENKINS-37423 Re: Connection refused when trying to release Having same issue when trying to release job-fan-in plugin. but environment is Windows 7 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37353) Last update of rvm-plugin disabled all my rvm configurations.
Title: Message Title Abel Paz commented on JENKINS-37353 Re: Last update of rvm-plugin disabled all my rvm configurations. Same here. All jobs that use the plugin (more than 50) were disabled: I saw that in config.xml this class changed (Jenkins::Plugin::Proxies::BuildWrapper by Jenkins::Tasks::BuildWrapperProxy): (before) "Jenkins::Plugin::Proxies::BuildWrapper" pluginid="rvm"> "RvmWrapper" pluginid="rvm"> "rvm" ruby-class="String">2.2.1@puppet "rvm" ruby-class="String">rvm (now) "Jenkins::Tasks::BuildWrapperProxy" pluginid="rvm"> "RvmWrapper" pluginid="rvm"> "rvm" ruby-class="String">2.2.1@puppet "rvm" ruby-class="String">rvm But even modifying it manually and reloading config from disk didn't work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop r
[JIRA] (JENKINS-37353) Last update of rvm-plugin disabled all my rvm configurations.
Title: Message Title
Abel Paz edited a comment on JENKINS-37353
Re: Last update of rvm-plugin disabled all my rvm configurations.
Same here. All jobs that use the plugin (more than 50) were failing because of the "rvm" check was disabled:I saw that in config.xml this class changed (Jenkins::Plugin::Proxies::BuildWrapper by Jenkins::Tasks::BuildWrapperProxy):(before){code:xml} 2.2.1@puppetrvm{code}(now){code:xml} 2.2.1@puppetrvm{code}But even modifying it manually and reloading config from disk didn't work.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35310) "Trigger builds remotely" doesn't save authToken
Title: Message Title Stefan Thurnherr commented on JENKINS-35310 Re: "Trigger builds remotely" doesn't save authToken Also confirming this issue, running Jenkins 2.18 with all plugins up-to-date. My usecase: Trying to use this to trigger builds upon push events in GitLab Community Edition, since the "Gitlab Hook Plugin" doesnt seem to work anyway for multi-branch projects, and anyway seems to be deprecated in favour of the "GitLab plugin" (but only available in GitLab EE). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23218) hetero-list for ProjectNamingStrategy
Title: Message Title Kanstantsin Shautsou stopped work on JENKINS-23218 Change By: Kanstantsin Shautsou Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37113) Failed to start TEST_SET
Title: Message Title Brice VIARD resolved as Fixed I resolved my issue, I created a lab managnement and changed the test set type from default to functional. Thanks again for your support on this subject. Best regards, Brice. Jenkins / JENKINS-37113 Failed to start TEST_SET Change By: Brice VIARD Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to je
[JIRA] (JENKINS-36831) Regression breakage in version number after upgrade
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36831 Re: Regression breakage in version number after upgrade Code changed in jenkins User: Deniz Bahadir Path: src/main/java/org/jvnet/hudson/tools/versionnumber/VersionNumberCommon.java http://jenkins-ci.org/commit/versionnumber-plugin/aa224390a913b6a95c65c4d1a57babd18c492bf6 Log: JENKINS-36831 Fixed regression. The meaning of the "skipFailedBuilds" flag was accidentally flipped. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33504) FATAL: missing dependencies
Title: Message Title Daniel Whatshisname commented on JENKINS-33504 Re: FATAL: missing dependencies I'm too stuck with FATAL: Unable to initialize command context. , although I have placed wildfly-cli 8.2.1.Final.jar in every place mentioned here. Can't understand why it is not possible for the deployer to fire up... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37353) Last update of rvm-plugin disabled all my rvm configurations.
Title: Message Title Benjamin Beermann commented on JENKINS-37353 Re: Last update of rvm-plugin disabled all my rvm configurations. Same here! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37580) Jenkins takes too long for loading recent changes of current job
Title: Message Title Mark Waite resolved as Not A Defect Please continue to use the mailing list for these types of questions. There are many more people reading the mailing list than there are reading the bug reports of individual plugins. Jenkins / JENKINS-37580 Jenkins takes too long for loading recent changes of current job Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group
[JIRA] (JENKINS-37348) conditional-build-step-plugin fail then try to fire another build
Title: Message Title Sergey Arbuzov closed an issue as Not A Defect Thanks a lot again Jenkins / JENKINS-37348 conditional-build-step-plugin fail then try to fire another build Change By: Sergey Arbuzov Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36831) Regression breakage in version number after upgrade
Title: Message Title Deniz Bahadir resolved as Fixed Jenkins / JENKINS-36831 Regression breakage in version number after upgrade Change By: Deniz Bahadir Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36831) Regression breakage in version number after upgrade
Title: Message Title Deniz Bahadir commented on JENKINS-36831 Re: Regression breakage in version number after upgrade This should be fixed in version 1.7.2. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36831) Regression breakage in version number after upgrade
Title: Message Title Deniz Bahadir assigned an issue to Deniz Bahadir Jenkins / JENKINS-36831 Regression breakage in version number after upgrade Change By: Deniz Bahadir Assignee: Deniz Bahadir Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36831) Regression breakage in version number after upgrade
Title: Message Title Deniz Bahadir started work on JENKINS-36831 Change By: Deniz Bahadir Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34829) Pipeline-Support for Version Number Plugin
Title: Message Title Deniz Bahadir closed an issue as Fixed Jenkins / JENKINS-34829 Pipeline-Support for Version Number Plugin Change By: Deniz Bahadir Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33699) Version Number Plugin
Title: Message Title Deniz Bahadir closed an issue as Duplicate Probably a duplicate of JENKINS-30224, and therefore already fixed in versions 1.6 and newer. Jenkins / JENKINS-33699 Version Number Plugin Change By: Deniz Bahadir Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https
[JIRA] (JENKINS-37299) TextFinder- & Claim-Plugin are not working properly together
Title: Message Title Moritz P commented on JENKINS-37299 Re: TextFinder- & Claim-Plugin are not working properly together Hi Christian Bremer, do you have any idea on how to fix this one and how long it might take? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemSometimes, after a certain amount of builds, the build never ends on the node. It sends forever the same 20-30 lines.It seems that the problem occures more when I restart Jenkins while there are some tasks running.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!_I think it's worth mentionning but I have 3 jenkins nodes on the same machine._h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!*Update 1:* It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.*Update 2:* It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!*Update 3:* It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... So it saves the log but interrupt the task, send to the slave that it has interrupted the task. The slave thinks that the logs has not been saved, and resend it to the master, which don't find the node workspace in it's local filesystem, etc. !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! *Update 4:* It seems that when the master deserializes the response of the node, it returns a null object instead of the logs when it comes to Wri
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemSometimes, after a certain amount of builds, the build never ends on the node. It sends forever the same 20-30 lines.It seems that the problem occures more when I restart Jenkins while there are some tasks running.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!_I think it's worth mentionning but I have 3 jenkins nodes on the same machine._h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!*Update 1:* It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.*Update 2:* It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!*Update 3:* It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... So it saves the log but interrupt the task, send to the slave that it has interrupted the task. The slave thinks that the logs has not been saved, and resend it to the master, which don't find the node workspace in it's local filesystem, etc. !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! *Update 4:* It seems that when the master deserializes the response of the node, it returns a null object instead of the logs when it comes to Wri
[JIRA] (JENKINS-36133) Animate in steps when stage node is clicked
Title: Message Title Thorsten Scherler started work on JENKINS-36133 Change By: Thorsten Scherler Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29956) Wipe out repository & force clone ignore's Windows directory junctions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29956 Re: Wipe out repository & force clone ignore's Windows directory junctions Code changed in jenkins User: dbroady1 Path: core/src/main/java/hudson/Util.java core/src/test/java/hudson/RemoveWindowsDirectoryJunctionTest.java http://jenkins-ci.org/commit/jenkins/f4edf91782720d2e1246ddb48554511912af1491 Log: JENKINS-29956 Test Windows junctions before Java 7 symlink (#1787) Test Windows junctions before Java 7 symlink Apparently Java 7 (and later) do not count Windows junctions as symlinks. When you drill down into the BasicFileAttributes structure, reparse points are only counted under isOther. So, since we already have code that properly detects Windows Junctions, let's use that first and then fallback to the Java 7 code. Add comment for change & link bug. Add test case Switch to Functions.isWindows(). Use non-deprecated APIs for tmp file/dir mgmt Add better debugging. Allow spaces in junction name & dir name. To do that, it was easier to use ProcessBuilder vs building up the correct string in code to send to cmd.exe. Also, I'll note that according to http://ss64.com/nt/syntax-internal.html, mklink is in internal cmd.exe command. So, it must be invoked through "cmd.exe /c" for it to work. Remove comment mentioning bug number. Remove debugging output, per Baptiste's request Add newline at end of file. Make sure that the junction was removed. Use assertEquals to show retcode of Process.waitFor.
[JIRA] (JENKINS-30019) It does not work with Jenkins Workflow jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30019 It does not work with Jenkins Workflow jobs Change By: Jesse Glick Labels: workflow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33504) FATAL: missing dependencies
Title: Message Title Daniel Whatshisname edited a comment on JENKINS-33504 Re: FATAL: missing dependencies I'm too stuck with FATAL: Unable to initialize command context. , although I have placed wildfly-cli 8.2.1.Final.jar in every place mentioned here. (I'm running Jenkins on x64 RedHat 7.0.1) Can't understand why it is not possible for the deployer to fire up... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10175) "Recording test results" is super slow, what is it doing?
Title: Message Title Marco Krikke commented on JENKINS-10175 Re: "Recording test results" is super slow, what is it doing? Has this been fixed in JENKINS-10234, or does this issue still exist? Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37477) PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail
Title: Message Title Greg Smith commented on JENKINS-37477 Re: PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail One other thing I'll mention: The ability to choose "Build after other projects build" in the pipeline triggers snippet generator seem to be missing. I'm not sure if this is related or not - but maybe there's some kind of conflict between that option and the other new pipeline triggers that cause the docs / snippet generator to fail? I know that option was available recently, and is now gone. Anyway — thought I would add a list of the current properties values that I can currently see in the snippet generator, in case that give some clue to issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37477) PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-37477 PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail Change By: Greg Smith Attachment: Screen Shot 2016-08-22 at 9.36.12 AM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30019) It does not work with Jenkins Workflow jobs
Title: Message Title Jesse Glick resolved as Fixed Anyway, the compatibility issue was addressed. Jenkins / JENKINS-30019 It does not work with Jenkins Workflow jobs Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30019) It does not work with Jenkins Workflow jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30019 Re: It does not work with Jenkins Workflow jobs Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/3263e635ac649228f2d22164c92e36754a72c5d3 Log: JENKINS-30019 Noting merge of https://github.com/jenkinsci/next-build-number-plugin/pull/5. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36450) Unable to inject HP Application AUtomation Tools properties with attributes/environment variables
Title: Message Title
James Brown commented on JENKINS-36450
Re: Unable to inject HP Application AUtomation Tools properties with attributes/environment variables
Hi Roy Lu, Cathy wants to populate <_almUserName> and <_secret> of hp plugin with the credentials generated by Manage Jenkins >> Manage Credentials. HP Application Automation Tools Plugin code in the template: <__sseModel> <__almUserName>$ {almUserName} <__almPassword class="com.hp.application.automation.tools.model.SecretContainerImpl"> <__secret>$ {secret}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30019) It does not work with Jenkins Workflow jobs
Title: Message Title Jesse Glick commented on JENKINS-30019 Re: It does not work with Jenkins Workflow jobs The issue with multibranch Pipelines is that the plugin is checking for Item.CONFIGURE but at best you will only have VIEW_CONFIGURATION on the branch projects, as they are generated. Which makes a sort of sense: setting the next build number is a kind of configuration change, and the design of multibranch projects is that branch projects are disposable and freely recreatable, containing no user configuration information. Maybe you should rethink why you are trying to set build numbers—via the UI!—in the first place. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30019) It does not work with Jenkins Workflow jobs
Title: Message Title Anna Tikhonova commented on JENKINS-30019 Re: It does not work with Jenkins Workflow jobs Jesse Glick Thanks! Setting custom build numbers makes sense for release branches sometimes. I've described the problem in JENKINS-33046. We want to bump master build numbers every time we branch a release out of it. The whole multibranch pipeline feature is super hot and we'd absolutely love to switch to it entirely, but still we'd like to keep the build number part of our workflow. Let me describe what it's like and why we want it. Assume our current master build number is N. We branch each release out of master and bump master build numbers to N + M, where M is a "window" that should be enough for this release branch lifetime. We do not build releases on each commit but every 4 hours, which makes it easy to make a fine estimate for M. This scheme makes build comparison straight-forward, by their build numbers. We can track where the branching has happened and determine where in commit history the particular build belongs (approx.) just by looking at its build number. Convenient because you can see if a patch was included into that particular build. Also, as Bryden Oliver has mentioned, build numbers might be visible to customers (which is true in our case as well, but we don't set them to something like '43p1'; we just bump the standard numerical build numbers in Jenkins), so I suppose many would like an opportunity to control them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Stan Domula commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials I saw that the fix was merged, is there a schedule for when the plugin gets a new release? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemSometimes, after a certain amount of builds, the build never ends on the node. It sends forever the same 20-30 lines.It seems that the problem occures more when I restart Jenkins while there are some tasks running.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!_I think it's worth mentionning but I have 3 jenkins nodes on the same machine._h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!*Update 1:* It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.*Update 2:* It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!*Update 3:* It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... So it saves the log but interrupt the task, send to the slave that it has interrupted the task. The slave thinks that the logs has not been saved, and resend it to the master, which don't find the node workspace in it's local filesystem, etc. !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! *Update 4:* It seems that when the master deserializes the response of the node, it returns a null object instead of the logs when it comes to Wri
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemSometimes, after a certain amount of builds, the build never ends on the node. It sends forever the same 20-30 lines.It seems that the problem occures more when I restart Jenkins while there are some tasks running.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!_I think it's worth mentionning but I have 3 jenkins nodes on the same machine._h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!*Update 1:* It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.*Update 2:* It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!*Update 3:* It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... So it saves the log but interrupt the task, send to the slave that it has interrupted the task. The slave thinks that the logs has not been saved, and resend it to the master, which don't find the node workspace in it's local filesystem, etc. !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! *Update 4:* It seems that when the master deserializes the response of the node, it returns a null object instead of the logs when it comes to Wri
[JIRA] (JENKINS-37587) Triggered job cannot be displayed in pipeline view if called job name contains a variable
Title: Message Title
Nicolas Haumont created an issue
Jenkins / JENKINS-37587
Triggered job cannot be displayed in pipeline view if called job name contains a variable
Issue Type:
New Feature
Assignee:
Unassigned
Components:
build-pipeline-plugin
Created:
2016/Aug/22 2:10 PM
Priority:
Minor
Reporter:
Nicolas Haumont
Hi, It might be possible already but could not figure how to manage it. I have a project named "A" that triggers another job, but using a parameter for the job name, so, A triggers B_$ {branch} When creating the pipeline with job A as initial job, the pipeline view cannot display for instance the B_master job that is triggered by A. It's probably caused by the fact there is a variable in the job name. Would it be possible to handle that type of use case, or is there any workaround for that? Thanks
Add Comment
[JIRA] (JENKINS-37423) Connection refused when trying to release
Title: Message Title CrossBrowserTesting.com LLC commented on JENKINS-37423 Re: Connection refused when trying to release fixed it. had to update the parent to version to at least 2.5 in pom.xml https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37423) Connection refused when trying to release
Title: Message Title CrossBrowserTesting.com LLC resolved as Not A Defect fixed it. had to update the parent to version of at least 2.5 in pom.xml https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues Jenkins / JENKINS-37423 Connection refused when trying to release Change By: CrossBrowserTesting.com LLC Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this grou
[JIRA] (JENKINS-37585) Allow support for "alpha", "beta" and "RC" versions of jenkins-core
Title: Message Title Raul Arabaolaza updated JENKINS-37585 Jenkins / JENKINS-37585 Allow support for "alpha", "beta" and "RC" versions of jenkins-core Change By: Raul Arabaolaza Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37423) Connection refused when trying to release
Title: Message Title CrossBrowserTesting.com LLC edited a comment on JENKINS-37423 Re: Connection refused when trying to release fixed it. had to update the parent to version to of at least 2.5 in pom.xml https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37568) Email Ext Plugin broke the Jenkins
Title: Message Title Trushar Patel commented on JENKINS-37568 Re: Email Ext Plugin broke the Jenkins Hello David, It turns out that one of the Jenkins job was configured wrong way and when i disable that job i don't see the issue anymore. Sorry for the false alarm. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37568) Email Ext Plugin broke the Jenkins
Title: Message Title Trushar Patel edited a comment on JENKINS-37568 Re: Email Ext Plugin broke the Jenkins Hello David,It turns out that one of the Jenkins job was configured wrong way and when i disable that job i don't see the issue anymore.And i didn't have the watching tuned on. Sorry for the false alarm. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37588) Multibranch pipleine does not allow quiet time or throttle
Title: Message Title Brian Sipos created an issue Jenkins / JENKINS-37588 Multibranch pipleine does not allow quiet time or throttle Issue Type: Improvement Assignee: Oleg Nenashev Components: pipeline-_unsorted Created: 2016/Aug/22 2:45 PM Environment: Running jenkins 2.15 with pipeline-multibranch 2.8. Priority: Major Reporter: Brian Sipos Currently, for an individual pipeline job I can set a quiet time to avoid one-for-one commit-to-build ratio when there are many commits in a short time. I like to use the multibranch plugin to allow branch automation, but there does not appear to be a way for a multibranch config (either the meta-job itself or from within a Jenkinsfile) to define a quiet time or some other ability to throttle job runs. Add Comment
[JIRA] (JENKINS-35475) Multibranch pipeline displays SCM views multiple times
Title: Message Title Brian Sipos commented on JENKINS-35475 Re: Multibranch pipeline displays SCM views multiple times I think I see the same issue but due to different config. I use SVN as repository and have a multibranch-detected Jenkinsfile with a simple "checkout scm" step that also shows up with duplicated job change entries (exactly two as seen in this original ticket). I can attach screenshot of my views if it helps. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37423) Connection refused when trying to release
Title: Message Title CrossBrowserTesting.com LLC updated an issue Jenkins / JENKINS-37423 Connection refused when trying to release Change By: CrossBrowserTesting.com LLC Comment: fixed it. had to update the parent to version of at least 2.5 in pom.xml https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37589) Replay link does not show up if Jenkinsfile had a syntax error
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-37589 Replay link does not show up if Jenkinsfile had a syntax error Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/22 2:54 PM Labels: community-bee Priority: Minor Reporter: R. Tyler Croy Steps to reproduce Create a Pipeline with a Jenkinsfile Introduce a Groovy syntax error, like omitting a trailing parenthesis on a method call Execute What ends up happening is that an exception is shown, e.g.: Checking out Revision f29c250737c3db53f709977224c4547a43ed4886 (refs/remotes/origin/master) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 7: expecting ')', found ']' @ line 7, column 17. ]) But the sidebar includes no Replay link to attempt to fix the change, instead you need to commit a change to make the Jenkinsfile correct Groovy syntax. Expected Replay is shown no matter how fscked my Jenkinsfile is so I can correct it This issue al
[JIRA] (JENKINS-36823) Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles
Title: Message Title Brian Holt started work on JENKINS-36823 Change By: Brian Holt Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37590) RuntimeException Error if you attempt to save a parameterized build with no parameters
Title: Message Title
John Hill created an issue
Jenkins / JENKINS-37590
RuntimeException Error if you attempt to save a parameterized build with no parameters
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Aug/22 3:13 PM
Environment:
Linux
Labels:
jenkins
Priority:
Minor
Reporter:
John Hill
1. Edit a job's configuration 2. Select the 'This build is parameterized' checkbox 3. Save the configuration You get a RuntimeException and stack trace. A more user-friendly error would be preferable. It took me a few minutes to realize my mistake. Full stack trace:
javax.servlet.ServletException: java.lang.Error: Failed to instantiate class hudson.model.ParametersDefinitionProperty from {"specified":true}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
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:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at org.eclipse.jetty.servlet.ServletHandle
[JIRA] (JENKINS-37590) RuntimeException Error if you attempt to save a parameterized build with no parameters
Title: Message Title John Hill commented on JENKINS-37590 Re: RuntimeException Error if you attempt to save a parameterized build with no parameters Seemingly a regression Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37588) Multibranch pipleine does not allow quiet time or throttle
Title: Message Title Oleg Nenashev commented on JENKINS-37588 Re: Multibranch pipleine does not allow quiet time or throttle Changed the component. Actually there are many throttling options in Pipeline, but Quite Period is definitely not one of them Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
