[JIRA] (JENKINS-38656) Can't build with JDK 1.6
Title: Message Title Andrea Mariottini assigned an issue to Unassigned Jenkins / JENKINS-38656 Can't build with JDK 1.6 Change By: Andrea Mariottini Assignee: Eyal Ben Moshe 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-38703) [INFO] Deploying artifact not workign with http forwarding proxy
Title: Message Title Jordi Redondo commented on JENKINS-38703 Re: [INFO] Deploying artifact not workign with http forwarding proxy Hi, As I did read different literature about the proxy usage and results on settings.xml, I tried to test under the below three scenarios (once at time). One scenario with HTTP, other with HTTPS and other with HTTPS. The target URL I tried to use from Artifactory it is HTTPS. proxies> myhttpproxy true http myhost 8080 localhost proxies> myhttpproxy true https myhost 8080 localhost proxies> myhttpproxy true * myhost 8080 localhost One interesting aspect to remark. I tried to inject to artifactory by command line script section at jenkins job, and it works, but if I try from Artifactory plugin, it simply ignores the proxy and tries to artifact directly bypassing the proxy. 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-38313) External Build Log storage for Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38313 External Build Log storage for Jenkins Change By: Oleg Nenashev Jenkins' logging system is one of potential scalability bottlenecks on big Jenkins instances. System logging can be redirected via JUL log appenders (or other such solutions), but there is no OOTB solution for build logs.It would be great to have such solution. Top-level requirements: * All or almost all build/task logging is moved from Jenkins filesystem to External Build Log Storage * Minimize log traffic between Jenkins agents and the master, logs should be reported from slaves directly when it is possible* External Build Log Storage has an extensible and pluggable architecture* At least 2 reference implementations: ** File-system-based storage (current implementation) ** One external build log storage based on the open-source stack. Preference - Elasticsearch-Logstash-Kibana* Jenkins Pipeline is supported out of the box* Old logs should be browseable after changing the storage engine (Migration or parallel engines) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38313) External Build Log storage for Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38313 External Build Log storage for Jenkins Change By: Oleg Nenashev Jenkins' logging system is one of potential scalability bottlenecks on big Jenkins instances. System logging can be redirected via JUL log appenders (or other such solutions), but there is no OOTB solution for build logs.It would be great to have such solution. Top-level requirements:* All or almost all build/task logging is moved from Jenkins filesystem to External Build Log Storage* Minimize log traffic between Jenkins agents and the master, logs should be reported from slaves directly when it is possible* External Build Log Storage has an extensible and pluggable architecture* At least 2 reference implementations: ** File-system-based storage (current implementation) ** One external build log storage based on the open-source stack. Preference - Elasticsearch-Logstash-Kibana* Jenkins Pipeline is supported out of the box* Old logs should be browseable after changing the storage engine (Migration or parallel engines) Design document:* https://docs.google.com/document/d/1_bquSeA_lC7zJhQoWhxlSKJAg6b8duNbyQ15zCz-e4Y/edit# Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-6819) Jobs are triggered twice occasionally
Title: Message Title Luis Panadero Guardeño commented on JENKINS-6819 Re: Jobs are triggered twice occasionally Happening on 2.7.4 . I'm trying to update git plugins to see if fix this . We aren't using SCM polling. It's a task scheduled to be executed only one time per day, that was working fine before we change the git branch that is checked. It's very annoying as it's a heavy task that enters on a infinite loop. The duplicated jobs shows that Jenkins detected changes on the repository, but not show any change. 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-6819) Jobs are triggered twice occasionally
Title: Message Title Luis Panadero Guardeño edited a comment on JENKINS-6819 Re: Jobs are triggered twice occasionally Happening on 2.7.4 . I'm trying to update git plugins to see if fix this . We aren't using SCM polling. It's a task scheduled to be executed only one time per day, that was working fine before we change the git branch that is checked. It's very annoying as it's a heavy task that enters on a infinite loop. The duplicated jobs shows that Jenkins detected changes on the repository, but not show any change. UPDATE : Updating the git plug-in don't fix this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38655) org.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS
Title: Message Title Ben Empson commented on JENKINS-38655 Re: org.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS The scenario is not using TFS with special chars in the password. Yes, _ and ! were the only special chars present. No other hints - this was a vanilla installation and the first project I setup in it. Changing to JGit resolved the problem. I believe that the remote git server is Linux but it's a 3rd-party service. Seems likely that this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-38194 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-38655) org.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS
Title: Message Title Ben Empson edited a comment on JENKINS-38655 Re: org.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS The scenario is not using TFS with special chars in the password. Yes, _ and ! were the only special chars present. No other hints - this was a vanilla installation and the first project I setup in it. Changing to JGit resolved the problem. I believe that the remote git server is Linux but it's a 3rd-party service. Seems likely that this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-38194 - I note that the error stacktrace shows the use of GIT_ASKPASS in my scenario also - this was mentioned in 38194. 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-38684) @WithOS not working if multiple OS given
Title: Message Title Manuel Franco resolved as Fixed Jenkins / JENKINS-38684 @WithOS not working if multiple OS given Change By: Manuel Franco 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-38722) build is trigerred uppon merge commit despite no change in included files
Title: Message Title
Lubo Varga created an issue
Jenkins / JENKINS-38722
build is trigerred uppon merge commit despite no change in included files
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Oct/05 7:50 AM
Labels:
git
Priority:
Major
Reporter:
Lubo Varga
I have configured project, where in csm I have Additional Behaviours -> Pooling ignores commits in certain paths with Included Regions pointing to one specific file. I have there also additional behaviour "Clean before checkout". When post-receive hook triggers change, everything works as expected. Pool SCM schedule is set to "H/1 * * * *" (each hour). Yesterday I have found that build has been started in night despite no changes was made to given file. In pool log for given build is this:
Started on Oct 4, 2016 3:11:54 PM
Polling SCM changes on master
Using strategy: Default
[poll] Last Built Revision: Revision 5eb3f4c485189f8151d0fe777a31bcfc48adb09e (origin/master)
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repositories
> git config remote.origin.url ssh://g...@dev.asdf.sk/~/salt.git/ # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from ssh://g...@dev.asdf.sk/~/salt.git/
> git --version # timeout=10
> git fetch --tags --progress ssh://g...@dev.asdf.sk/~/salt.git/ +refs/heads/*:refs/remotes/origin/*
Polling for changes in
> git rev-parse origin/master^{commit} # timeout=10
> git log --full-history --no-abbrev --form
[JIRA] (JENKINS-6819) Jobs are triggered twice occasionally
Title: Message Title Luis Panadero Guardeño commented on JENKINS-6819 Re: Jobs are triggered twice occasionally Looks that gets fixed if I clean the workshop. I would say tomorrow. 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-38693) MissingResourceException running Artifactory Release Staging
Title: Message Title Jan Dittberner updated an issue Jenkins / JENKINS-38693 MissingResourceException running Artifactory Release Staging Change By: Jan Dittberner Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6819) Jobs are triggered twice occasionally
Title: Message Title Luis Panadero Guardeño edited a comment on JENKINS-6819 Re: Jobs are triggered twice occasionally Looks that gets fixed if I clean the workshop workspace . I would say tomorrow. 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-38722) build is trigerred uppon merge commit despite no change in included files
Title: Message Title Lubo Varga commented on JENKINS-38722 Re: build is trigerred uppon merge commit despite no change in included files Found probably issues which are same as my. 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-38723) Stash failed with IOException during scalability testing
Title: Message Title
Alvaro Lobato created an issue
Jenkins / JENKINS-38723
Stash failed with IOException during scalability testing
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2016/Oct/05 8:22 AM
Priority:
Minor
Reporter:
Alvaro Lobato
During an scalability test, one of the executions failed on stash while executing this pipeline script in a high concurrency environment (15 nodes and 4 executors and a start queue of about 700 jobs)
def branch(name) {
return {
node {
sh "sleep 30 && head -c 52428800 /dev/urandom > ${name}.bin"
stash includes: "${name}.bin", name: "${name}"
}
}
}
stage "Thinking"
for (i = 0; i < 5; i++) {
sleep time: 250, unit: 'MILLISECONDS'
echo "Thinking $i"
}
stage "Working"
def branches = [:]
branches["b1"] = branch("b1")
branches["b2"] = branch("b2")
branches["b3"] = branch("b3")
parallel branches
stage "Resting"
for (i = 0; i < 5; i++) {
sleep time: 150, unit: 'MILLISECONDS'
echo "Resting $i"
}
This was the result of the execution:
Started
[Pipeline] stage (Thinking)
Entering stage Thinking
Proceeding
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 0
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 1
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 2
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 3
[Pipeline] sleep
Sleeping for 0.25 sec
[Pipeline] echo
Thinking 4
[Pipeline] stage (Working)
Entering stage Working
Proceeding
[Pipeline] parall
[JIRA] (JENKINS-38724) Make ATH great again
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38724 Make ATH great again Issue Type: Task Assignee: Thorsten Scherler Components: blueocean-plugin Created: 2016/Oct/05 8:28 AM Priority: Major Reporter: Michael Neale It would be good to improve the "trust ability" of the ATH. In scope: Identify and remove known flaky timing based tests Add tests that are simple and less timing sensitive Make ATH great again! (general placeholder ticket for improvement). Add Comment
[JIRA] (JENKINS-36766) Developer can get a link to the PR and Branch on Github
Title: Message Title Michael Neale commented on JENKINS-36766 Re: Developer can get a link to the PR and Branch on Github Temporarily flicking to brody as a design for this is needed but not available 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-36766) Developer can get a link to the PR and Branch on Github
Title: Message Title Michael Neale assigned an issue to Brody Maclean Jenkins / JENKINS-36766 Developer can get a link to the PR and Branch on Github Change By: Michael Neale Assignee: Thorsten Scherler Brody Maclean 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-37788) Pipeline Config: Eliminate the "isConstant" AST/JSON field
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37788 Re: Pipeline Config: Eliminate the "isConstant" AST/JSON field Code changed in jenkins User: Andrew Bayer Path: src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTValue.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidator.groovy src/main/resources/ast-schema.json src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/validator/JSONValidationTest.java src/test/resources/json/agentAny.json src/test/resources/json/agentDocker.json src/test/resources/json/agentLabel.json src/test/resources/json/agentNoneWithNode.json src/test/resources/json/errors/emptyEnvironment.json src/test/resources/json/errors/emptyNotifications.json src/test/resources/json/errors/emptyParallel.json src/test/resources/json/errors/emptyPostBuild.json src/test/resources/json/errors/emptyStages.json src/test/resources/json/errors/invalidBuildCondition.json src/test/resources/json/errors/malformed.json src/test/resources/json/errors/missingAgent.json src/test/resources/json/errors/missingRequiredStepParameters.json src/test/resources/json/errors/missingStages.json src/test/resources/json/errors/notInstalledToolType.json src/test/resources/json/errors/notInstalledToolVersion.json src/test/resources/json/errors/rejectParallelMixedInSteps.json src/test/resources/json/errors/rejectStageInSteps.json src/test/resources/json/errors/stageWithoutName.json src/test/resources/json/errors/unknownStepParameter.json src/test/resources/json/errors/unlistedToolType.json src/test/resources/json/globalLibrarySuccess.json src/test/resources/json/legacyMetaStepSyntax.json src/test/resources/json/metaStepSyntax.json src/test/resources/json/parallelPipeline.json src/test/resources/json/postBuildAndNotifications.json src/test/resources/json/simpleEnvironment.json src/test/resources/json/simpleNotification.json src/test/resources/json/simplePipeline.json src/test/resources/json/simplePostBuild.json src/test/resources/json/simpleScript.json src/test/resources/json/simpleTools.json src/test/resources/json/twoStagePipeline.json src/test/resources/json/validStepParameters.json http://jenkins-ci.org/commit/pipeline-model-definition-plugin/670ecdb55ea6b5ab7e9083fd44079af61fe229c0 Log: [FIXED JENKINS-37788] Use isLiteral instead of isConstant. Add Comment
[JIRA] (JENKINS-36766) Developer can get a link to the PR and Branch on Github
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36766 Developer can get a link to the PR and Branch on Github Change By: Michael Neale Sprint: pacific atlantic 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-38724) Make ATH great again
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38724 Make ATH great again Change By: Michael Neale Sprint: pacific 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-38725) JS docs for javascript code in blueocean modules
Title: Message Title Michael Neale assigned an issue to Thorsten Scherler Jenkins / JENKINS-38725 JS docs for _javascript_ code in blueocean modules Change By: Michael Neale Assignee: 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-38725) JS docs for javascript code in blueocean modules
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38725 JS docs for _javascript_ code in blueocean modules Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/05 8:40 AM Priority: Minor Reporter: Michael Neale As pointed out but Thorsten "would you trust a java library or tools that had 0 javadocs" - it may make sense to use js docs to document important modules, methods or public apis. This could yield documentation similar to what the ATH has, served by github here: https://jenkinsci.github.io/blueocean-acceptance-test/page_objects.module_folderCreate.html https://jenkinsci.github.io/blueocean-acceptance-test/index.html source: https://github.com/jenkinsci/blueocean-acceptance-test/blob/master/src/main/js/page_objects/classic_jenkins/folderCreate.js In scope: documentation in comments for important modules Generation of HTML docs from these comments and publishing Add Comment
[JIRA] (JENKINS-38725) JS docs for javascript code in blueocean modules
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38725 JS docs for _javascript_ code in blueocean modules Change By: Michael Neale Sprint: indian 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-38482) Documentation of ExtensionPoints and their attributes they get passed (data types)
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38482
Documentation of ExtensionPoints and their attributes they get passed (data types)
Change By:
Michael Neale
ExtensionPoints are an important part of the JS side of plugins in blue ocean, they should be documented in terms of what data they can get passed and where they are hosted. In scope: * Find a scheme to document extension points, including param types* Find a mechanism to generate static docs from source of what extension points are available, and what module, and publish* Find a mechanism to dynamically enumerate extensionpoints and current implementers in a running jenkins instance on a "special" URI IN https://github.com/jenkinsci/blueocean-plugin/pull/521{quote}I take the point which leads to "contract properties" passed to certain ExtensionPoints. ATM we do it on free guess and all properties are passed through anyway.However we do not have API style declarations of extension points and the attributes we pass through. Which makes it hard for adopters to create reliable alternatives for our default implementations.I say ATM the graph is the only use case that we know of that had used run.id in a certain point of time. For housekeeping I prefer to get rid of it since it is redundant now because we pass full run.As started I see your point, but see as well the urgent need to declare ExtensionPoints as API where we can deprecate certain attributes to later drop them. ...and to document them to start with.{quote}in case you see the urge [~michaelneale] please assign to final implementer otherwise just close it.
Add Comment
[JIRA] (JENKINS-38482) Documentation of ExtensionPoints and their attributes they get passed (data types)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38482 Documentation of ExtensionPoints and their attributes they get passed (data types) Change By: Michael Neale Sprint: atlantic 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-38726) Does not allow "execute shell" scripts without #!/bin/foo header
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-38726 Does not allow "execute shell" scripts without #!/bin/foo header Issue Type: New Feature Assignee: Unassigned Components: cygpath-plugin Created: 2016/Oct/05 9:00 AM Priority: Minor Reporter: Jo Shields A recent update to Jenkins means the "Execute shell" script no longer executes "/bin/sh" by default - it executes "sh" As a result, the CygPath plugin no longer works, for any scripts which don't include a #!/bin/foo shell as an explicit override. Add Comment
[JIRA] (JENKINS-38727) FindBugs does not collects analysis results
Title: Message Title Waldemar Prabucki created an issue Jenkins / JENKINS-38727 FindBugs does not collects analysis results Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 2016/Oct/05 9:19 AM Environment: FindBugs.4.65 Jenkins 2.7.4 maven-findbugs-plugin 2.5.5 Java 1.7 Priority: Critical Reporter: Waldemar Prabucki For Maven Project FindBugs does not collects analysis results. The Problems are shown in console but not parsed and shown in job results. Maven goals: clean site install -Dmaven.javadoc.skip=true -Dsoe.env.Unit-Test-Environment=CI --fail-never -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser SaxParser beacuse of problem with SaxParser (another Issue) [INFO] [INFO] --- findbugs-maven-plugin:2.5.5:findbugs (findbugs) @ XxxxImpl --- [INFO] Fork Value is true [java] Warnings generated: 1 [INFO] Done FindBugs Analysis [FINDBUGS] Finding all files that match the pattern findbugsXml.xml [FINDBUGS] Parsing 1 file in /root/.jenkins/workspace/A_CI/XxxxImpl/target [FINDBUGS] Successfully parsed file /root/.jenkins/workspace/A_CI/XxxxImpl/target/findbugsXml.xml of module XxxxImpl with 0 unique warnings and 0 duplicates. [FINDBUGS] Computing warning deltas based on reference build #3380 [PMD] No report found for mojo check [
[JIRA] (JENKINS-38674) GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps
Title: Message Title Kirill Merkushev commented on JENKINS-38674 Re: GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps You can use variables and not hardcode 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-38727) FindBugs does not collects analysis results
Title: Message Title Ulli Hafner commented on JENKINS-38727 Re: FindBugs does not collects analysis results The site goal is not supported with the maven project type. Can't you run the findbugs:findbugs goal? 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-38728) FindBugs fails to load SaxParser
Title: Message Title Waldemar Prabucki created an issue Jenkins / JENKINS-38728 FindBugs fails to load SaxParser Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 2016/Oct/05 9:33 AM Environment: FindBugs.4.65 Jenkins 2.7.4 maven-findbugs-plugin 2.5.5 Java 1.7 Priority: Critical Reporter: Waldemar Prabucki For Maven Project FindBugs does not collects analysis results. The Problems are shown in console but not parsed and shown in job results. Maven goals: clean site install -Dmaven.javadoc.skip=true -Dsoe.env.Unit-Test-Environment=CI --fail-never -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser SaxParser beacuse of problem with SaxParser (another Issue) [INFO] [INFO] --- findbugs-maven-plugin:2.5.5:findbugs (findbugs) @ XxxxImpl --- [INFO] Fork Value is true [java] Warnings generated: 1 [INFO] Done FindBugs Analysis [FINDBUGS] Finding all files that match the pattern findbugsXml.xml [FINDBUGS] Parsing 1 file in /root/.jenkins/workspace/A_CI/XxxxImpl/target [FINDBUGS] Successfully parsed file /root/.jenkins/workspace/A_CI/XxxxImpl/target/findbugsXml.xml of module XxxxImpl with 0 unique warnings and 0 duplicates. [FINDBUGS] Computing warning deltas based on reference build #3380 [PMD] No report found for mojo check [INFO] [INFO
[JIRA] (JENKINS-38728) FindBugs fails to load SaxParser
Title: Message Title
Waldemar Prabucki updated an issue
Jenkins / JENKINS-38728
FindBugs fails to load SaxParser
Change By:
Waldemar Prabucki
For Maven Project FindBugs does not collects analysis results.The Problems are shown in console but not parsed fails to load SaxParser and shown in job results breaks future parser uses .Maven goals: {code}clean site install -Dmaven.javadoc.skip=true -Dsoe.env.Unit-Test-Environment=CI --fail-never -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser{code} SaxParser beacuse of problem with SaxParser (another Issue) {code}[INFO] [INFO] --- findbugs- maven- checkstyle- plugin:2. 5.5 15 : findbugs check ( findbugs default ) @ XxxxImpl ---[INFO] Fork Value is true [java] Warnings generated: 1[INFO] Done FindBugs Analysis Starting audit ... . [FINDBUGS] Finding all files that match the pattern findbugsXml Audit done . xml [ FINDBUGS CHECKSTYLE ] Parsing 1 file in /root/.jenkins/workspace/ A_CI A_CI_Individual_1 /XxxxImpl/target /checkstyle-result.xml [ FINDBUGS CHECKSTYLE ] Successfully parsed file /root/.jenkins/workspace/ A_CI A_CI_Individual_1 /XxxxImpl/target/ findbugsXml checkstyle-result .xml of module XxxxImpl with 0 unique warnings and 0 duplicates.[ FINDBUGS CHECKSTYLE ] Computing warning deltas based on reference build # 3380 768 [PMD] No report found for mojo check[INFO] [INFO] --- findbugs-maven-plugin:2.5.5: check findbugs ( default findbugs ) @ XxxxImpl ---[INFO] BugInstance size Fork Value is 1 true [INFO] Error size is 0 Done FindBugs Analysis [INFO] Total bugs Warning : Caught exception attempting to use SAX to load a SAX XMLReader Warning: Exception was: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: Classloading from system classloader disabledWarning: I will print the stack trace then carry on using the default SAX parserorg.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: Classloading from system classloader disabled at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:229) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:190) at org.dom4j.io.SAXHelper.createXMLReader(SAXHelper.java:83) at org.dom4j.io.SAXReader.createXMLReader(SAXReader.java:894) at org.dom4j.io.SAXReader.getXMLReader(SAXReader.java:715) at org.dom4j.io.SAXReader.read(SAXReader.java:435) at org.dom4j.io.SAXReader.read(SAXReader.java:365) at edu.umd.cs.findbugs.PluginLoader.getPluginDescriptor(PluginLoader.java:1145) at edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:636) at edu.umd.cs.findbugs.PluginLoader.(PluginLoader.java:397) at edu.umd.cs.findbugs.PluginLoader.loadCorePlugin(PluginLoader.java:1433) at edu.umd.cs.findbugs.PluginLoader.loadInitialPlugins(PluginLoader.java:1387) at edu.umd.cs.findbugs.PluginLoader.(PluginLoader.java:154) at edu.umd.cs.findbugs.DetectorFactoryCollection.getCoreResource(DetectorFactoryCo
[JIRA] (JENKINS-38728) FindBugs fails to load SaxParser
Title: Message Title
Waldemar Prabucki updated an issue
Jenkins / JENKINS-38728
FindBugs fails to load SaxParser
Change By:
Waldemar Prabucki
For Maven Project FindBugs fails to load SaxParser and breaks future parser uses.Maven goals: {code}clean site install -Dmaven.javadoc.skip=true -Dsoe.env.Unit-Test-Environment=CI --fail-never -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser {code}{code}[INFO] [INFO] --- maven-checkstyle-plugin:2.15:check (default) @ XxxxImpl ---[INFO] Starting audit...Audit done.[CHECKSTYLE] Parsing file /root/.jenkins/workspace/A_CI_Individual_1/XxxxImpl/target/checkstyle-result.xml[CHECKSTYLE] Successfully parsed file /root/.jenkins/workspace/A_CI_Individual_1/XxxxImpl/target/checkstyle-result.xml of module XxxxImpl with 0 unique warnings and 0 duplicates.[CHECKSTYLE] Computing warning deltas based on reference build #768[PMD] No report found for mojo check[INFO] [INFO] --- findbugs-maven-plugin:2.5.5:findbugs (findbugs) @ XxxxImpl ---[INFO] Fork Value is true[INFO] Done FindBugs AnalysisWarning: Caught exception attempting to use SAX to load a SAX XMLReader Warning: Exception was: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: Classloading from system classloader disabledWarning: I will print the stack trace then carry on using the default SAX parserorg.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: Classloading from system classloader disabled at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:229) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:190) at org.dom4j.io.SAXHelper.createXMLReader(SAXHelper.java:83) at org.dom4j.io.SAXReader.createXMLReader(SAXReader.java:894) at org.dom4j.io.SAXReader.getXMLReader(SAXReader.java:715) at org.dom4j.io.SAXReader.read(SAXReader.java:435) at org.dom4j.io.SAXReader.read(SAXReader.java:365) at edu.umd.cs.findbugs.PluginLoader.getPluginDescriptor(PluginLoader.java:1145) at edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:636) at edu.umd.cs.findbugs.PluginLoader.(PluginLoader.java:397) at edu.umd.cs.findbugs.PluginLoader.loadCorePlugin(PluginLoader.java:1433) at edu.umd.cs.findbugs.PluginLoader.loadInitialPlugins(PluginLoader.java:1387) at edu.umd.cs.findbugs.PluginLoader.(PluginLoader.java:154) at edu.umd.cs.findbugs.DetectorFactoryCollection.getCoreResource(DetectorFactoryCollection.java:360) at edu.umd.cs.findbugs.SystemProperties.loadPropertiesFromConfigFile(SystemProperties.java:77) at edu.umd.cs.findbugs.SystemProperties.(SystemProperties.java:60) at edu.umd.cs.findbugs.SortedBugCollection.(SortedBugCollection.java:96) at hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:368) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:266) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:204) at hudson.plugins.findbugs.parser.F
[JIRA] (JENKINS-38564) API to convert json step blob to step syntax (and back) - one step at a time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38564 Re: API to convert json step blob to step syntax (and back) - one step at a time Code changed in jenkins User: Robert Sandell Path: src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterAction.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterActionStepsTest.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/util/IsJsonObjectContaining.java src/test/resources/json/steps/arrayEcho.json src/test/resources/json/steps/simpleEcho.json src/test/resources/json/steps/simpleScript.json http://jenkins-ci.org/commit/pipeline-model-definition-plugin/0f7fcb36f52b71c272a3c0143be19679a37badde Log: JENKINS-38564 Steps from JSON to Jenkinsfile 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-38564) API to convert json step blob to step syntax (and back) - one step at a time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38564 Re: API to convert json step blob to step syntax (and back) - one step at a time Code changed in jenkins User: Robert Sandell Path: src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Converter.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterAction.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterActionStepsTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/b4682fcbc7789a4fa8fe5bfe4b747aad996a4d64 Log: JENKINS-38564 Jenkinsfile steps to json Compare: https://github.com/jenkinsci/pipeline-model-definition-plugin/compare/0f7fcb36f52b^...b4682fcbc778 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-38729) Jobs not dequeued when all executors are free
Title: Message Title Puneeth Nanjundaswamy created an issue Jenkins / JENKINS-38729 Jobs not dequeued when all executors are free Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 2016/Oct/05 9:48 AM Environment: Jenkins: 2.7.1 Build Blocker Plugin: 1.7.3 Priority: Minor Reporter: Puneeth Nanjundaswamy Problem: I have two jobs that should not run in parallel. Job A runs when Job B is not running and vice versa. When no jobs are running and Job A queued (say when someone opens a PR) this job is always in the queue and not dequeued even though all the executors are free and no other job is running. This issue occurs when only this is the only job queued for execution in Jenkins. When a second job is queued, the first job starts executing. Seems like an issue with probing the queue. Workaround: The only effective workaround I could find was to have a dummy "hello world" job that runs every minute so that no jobs are always queued even though all executors are available and no conflicting jobs are running. Stacktrace: Oct 05, 2016 8:37:21 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.Queue$MaintainTask@3d40ed96 failed java.lang.NullPointerException at hudson.plugins.buildblocker.BlockingJobsMonitor.checkNodeForQueueEntries(BlockingJobsMonitor.java:108) at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.checkAccordingToProperties(BuildBlockerQueueTaskDispatcher.java:171) at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.checkForBlock(BuildBlockerQueueTaskDispatcher.java:127) at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canTake(BuildBlockerQueueTaskDispatcher.java:110) at hudson.model.Queue$JobOffer.canTake(Queue.java:258) at hudson.model.Queue.maintain(Queue.java:1532) at hudso
[JIRA] (JENKINS-38689) Failing test: JenkinsDatabaseSecurityRealmTest#login_and_logout
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38689 Re: Failing test: JenkinsDatabaseSecurityRealmTest#login_and_logout Code changed in jenkins User: Oliver Gondža Path: src/test/java/core/JenkinsDatabaseSecurityRealmTest.java http://jenkins-ci.org/commit/acceptance-test-harness/3dfdfd3290a1b6e27f1a59e97bda30281e31842f Log: Merge pull request #196 from mafraba/JENKINS-38689 JENKINS-38689 fix casing error Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/94884cfb03c6...3dfdfd3290a1 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-38689) Failing test: JenkinsDatabaseSecurityRealmTest#login_and_logout
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38689 Re: Failing test: JenkinsDatabaseSecurityRealmTest#login_and_logout Code changed in jenkins User: Manuel Franco Path: src/test/java/core/JenkinsDatabaseSecurityRealmTest.java http://jenkins-ci.org/commit/acceptance-test-harness/cf20a61f30e601bd06a2cdfcc3c12d37e62cc6dc Log: JENKINS-38689 fix casing error 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-38689) Failing test: JenkinsDatabaseSecurityRealmTest#login_and_logout
Title: Message Title Manuel Franco resolved as Fixed Jenkins / JENKINS-38689 Failing test: JenkinsDatabaseSecurityRealmTest#login_and_logout Change By: Manuel Franco 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-38592) pipelines data for json is getting a bit too crazy (for dashboard)
Title: Message Title Thorsten Scherler commented on JENKINS-38592 Re: pipelines data for json is getting a bit too crazy (for dashboard) Michael Neale yeah size does not matter ...that's what Jokes apart Cliff Meyers the problem is in support when bo fails. To review the informations of BO we need to review the server response and as said above there is way to much wood in the response. e.g. a "clean" response https://developer.github.com/v3/repos/forks/#create-a-fork https://www.thoughtworks.com/es/insights/blog/rest-api-design-resource-modeling is a nice article on how REST resources should be designed. I actually starting to thing that we should do 3 different requests for one resource and we fetch them separately ``` .../pipelines .../pipelines/links .../pipelines/actions ... ``` 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-38727) FindBugs does not collects analysis results
Title: Message Title Waldemar Prabucki commented on JENKINS-38727 Re: FindBugs does not collects analysis results We have auto activating profile in pom.xml which runs findbugs:check (as findbugs:findbugs is not fully supported by m2e-code-quality) and as long as I know findbugs:findbugs should be run only in report phase where check is being run during a build phase. 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-35415) Custom Jenkinsfile on multibranch project
Title: Message Title fahd arshad commented on JENKINS-35415 Re: Custom Jenkinsfile on multibranch project Is there any chance of getting this feature other than the Enterprise Jenkins? this is a pretty crucial feature. 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-38727) FindBugs does not collects analysis results
Title: Message Title
Waldemar Prabucki commented on JENKINS-38727
Re: FindBugs does not collects analysis results
QA profile in pom.xml:
STATIC-ANALYSIS
!no.analysis.static
org.apache.maven.plugins
maven-checkstyle-plugin
2.15
com.xxx
XXX-Build-Tools
0.2.0
true
xxx/checkstyle_checks.xml
xxx/checkstyle_suppressions.xml
org.apache.maven.plugins
maven-pmd-plugin
3.6
com.xxx
XXX-Build-Tools
0.2.0
true
true
1.6
xxx/pmd_ruleset.xml
com/daimler/xxx/foundation/common/types/message/*.java
com/daimler/xxx/foundation/common/types/*.java
com/daimler/xxx/vehicleproduct/enrichmentexternal/business/function/jaxb/uvsrequest/*.java
com/daimler/xxx/vehicleproduct/enrichmentexternal/business/function/jaxb/uvsresponse/*.java
com/daimler/xxx/vehicleproduct/enrichmentexternal/mock/*.java
com/daimler/xxx/vehicleproduct/externalvehicleconfiguration/mock/*.java
com/daimler/xxx/foundation/environment/business/service/mock/*.java
com/daimler/xxx/foundation/userandorg/mock/*.java
com/daimler/xxx/externalsystemsout/externalsystems/*.xml
daimler/.*
.*/gen/.*
.*/test-classes/.*
org.codehaus.mojo
findbugs-maven-plugin
2.5.5
com.xxx
XXX-Build-Tools
0.2.0
true
xxx/FindBugs_Classes.xml
xxx/FindBugs_Rules.xml
org.apache.maven.plugins
maven-checkstyle-plugin
check
verify
org.codehaus.mojo
findbugs-maven-plugin
check
verify
org.apache.maven.plugins
maven-pmd-plugin
check
verify
true
${project.build.directory}/site
org.apache.maven.plugins
maven-jxr-plugin
2.3
org.apache.maven.plugins
maven-javadoc-plugin
2.9
aggregate
aggregate
org.apache.maven.plugins
maven-project-info-reports-plugin
2.4
false
false
false
dependencies
scm
[JIRA] (JENKINS-38727) FindBugs does not collects analysis results
Title: Message Title Waldemar Prabucki updated an issue Jenkins / JENKINS-38727 FindBugs does not collects analysis results Change By: Waldemar Prabucki Environment: FindBugs.4.65Jenkins 2.7.4maven-findbugs-plugin 2.5.5Java 1.7 maven 3.0.3 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-38728) FindBugs fails to load SaxParser
Title: Message Title Waldemar Prabucki updated an issue Jenkins / JENKINS-38728 FindBugs fails to load SaxParser Change By: Waldemar Prabucki Environment: FindBugs.4.65Jenkins 2.7.4maven-findbugs-plugin 2.5.5Java 1.7 maven 3.0.3 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-38730) UX Login button
Title: Message Title Thorsten Scherler created an issue Jenkins / JENKINS-38730 UX Login button Issue Type: Improvement Assignee: Michael Neale Components: blueocean-plugin Created: 2016/Oct/05 10:30 AM Priority: Minor Reporter: Thorsten Scherler The login button in blueocean will redirect to the classic jenkins, however a better ux would be to open an "inline" form and never leave the BO page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38730) UX Login button
Title: Message Title Thorsten Scherler commented on JENKINS-38730 Re: UX Login button Further some in our office as well pointed out that the whole button should be enhanced 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-38730) UX Login button
Title: Message Title Thorsten Scherler updated an issue Jenkins / JENKINS-38730 UX Login button Change By: Thorsten Scherler Attachment: Screenshot from 2016-10-05 12-35-12.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-38731) Support uploading mappings to Google Play
Title: Message Title Anton Averin created an issue Jenkins / JENKINS-38731 Support uploading mappings to Google Play Issue Type: New Feature Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 2016/Oct/05 10:43 AM Priority: Minor Reporter: Anton Averin There should be a way to automatically upload proguard mappings to Google Play console Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35415) Custom Jenkinsfile on multibranch project
Title: Message Title
Jakub Pawłowski commented on JENKINS-35415
Re: Custom Jenkinsfile on multibranch project
As a workaround, you can have multpile Jenkinsfiles and Load the specific one based on JOB_NAME, like this:
node () {
checkout scm
if (env.JOB_NAME =~ 'myjob1') {
load 'myjob1.Jenkinsfile'
}
else if (env.JOB_NAME =~ 'myjob2') {
load 'myjob2.Jenkinsfile'
}
}()
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-38732) Add support for claiming a 'stage' within a pipeline job
Title: Message Title Richard Kettelerij created an issue Jenkins / JENKINS-38732 Add support for claiming a 'stage' within a pipeline job Issue Type: Improvement Assignee: Christian Bremer Components: claim-plugin Created: 2016/Oct/05 11:22 AM Labels: pipeline stage claim Priority: Minor Reporter: Richard Kettelerij The claim plugin currently operates on the job level (i.e. allow claiming of jobs). This is fine if you have a lot of small freestyle jobs. But with the new pipeline jobs (previously known as workflow jobs) you only have one job for your entire pipeline. The claim plugin already support claiming a failed pipeline job (JENKINS-27206) but this doesn't match a lot of use cases. Since pipeline jobs are made up of stages - and visualized as such by both the Stage View plugin and the new BlueOcean UI - it would ideal if you could claim a certain stage. I understand this may not be a trivial change since the concept of a stage isn't (yet?) as fundamental to Jenkins as jobs are. Nevertheless I think to a lot of folks claiming ownership of a failed stage would feel more natural than claiming the entire pipeline run.
[JIRA] (JENKINS-38732) Add support for claiming a 'stage' within a pipeline job
Title: Message Title Richard Kettelerij updated an issue Jenkins / JENKINS-38732 Add support for claiming a 'stage' within a pipeline job Change By: Richard Kettelerij 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-38732) Add support for claiming a 'stage' within a pipeline job
Title: Message Title Richard Kettelerij updated an issue Jenkins / JENKINS-38732 Add support for claiming a 'stage' within a pipeline job Change By: Richard Kettelerij The claim plugin currently operates on the job level (i.e. allow claiming of jobs). This is fine if you have a lot of small freestyle jobs. But with the new pipeline jobs (previously known as workflow jobs) you only have one job for your entire pipeline. The claim plugin already support claiming a failed pipeline job (JENKINS-27206) but this doesn't match a lot of align with every use cases case . Since pipeline jobs are made up of stages - and visualized as such by both the Stage View plugin and the new BlueOcean UI - it would ideal if you could claim a certain stage (ie . part of the pipeline). I understand this may not be a trivial change since the concept of a stage isn't (yet?) as fundamental to Jenkins as jobs are. Nevertheless I think to a lot of folks claiming ownership of a failed stage would feel more natural than claiming the entire pipeline run. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37461) Add support for pipeline in Task Scanner plugin
Title: Message Title Mike . updated an issue Jenkins / JENKINS-37461 Add support for pipeline in Task Scanner plugin Change By: Mike . Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28961) GET/POST with schedule-build-plugin
Title: Message Title James Coleman commented on JENKINS-28961 Re: GET/POST with schedule-build-plugin Thanks for working on a fix for this! Confirmed fixed BUT needed to disable CSRF Protection to get it to work. = test latest plugin built from source: problem if CSRF Protection is enabled = When attempting to schedule a job it fails (quietly) and I get this in jenkins log: Oct 05, 2016 12:13:32 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /job/##jobname##/build. Returning 403. So I guess a crumb/token needs to be posted with the request - in the case where CSRF protection is enabled. e.g. "Remote access with CSRF protection enabled" describes how to do it on command-line https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console = test latest plugin built from source: works if CSRF Protection is disabled = I suppose I could disable CSRF Protection . . . yes, it works if CSRF Protection is disabled. https://wiki.jenkins-ci.org/display/JENKINS/CSRF+Protection Oct 05, 2016 12:29:06 PM hudson.model.Run execute INFO: publish_system_test_regression_README_to_jenkins #101 main build action completed: SUCCESS = test latest plugin released: problem reproduced "plugin offered a GET link" = Earlier I reproduced the problem described on this bug with latest available Schedule Build Plugin. I installed Schedule Build Plugin yesterday (Wed Oct 4th). Version 0.3.4 (release dated 16 Sep 2015). Icons for Schedule Build appear okay if build scheduled I got a warning "plugin offered a GET link" as reported on this bug. There did appear to be some sort of a job scheduled and it said it "expires in Xhr/min. Waiting for Ymin/hr." which was correct for the time I scheduled. BUT It did not run the job. I couldn't find anything relevant in logs. Url, presumably the GET: http://jenkins:/job/jobname/build?delay=47212sec I'm using Jenkins 2.2 http://stackoverflow.com/questions/35029486/how-can-i-schedule-a-job-to-run-in-the-future-but-only-one-time-ever/39858002#39858002 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-28961) GET/POST with schedule-build-plugin
Title: Message Title James Coleman edited a comment on JENKINS-28961 Re: GET/POST with schedule-build-plugin Thanks for working on a fix for this!Confirmed fixed BUT needed to disable CSRF Protection to get it to work. :P= test latest plugin built from source: problem if CSRF Protection is enabled =When attempting to schedule a job it fails (quietly) and I get this in jenkins log:Oct 05, 2016 12:13:32 PM hudson.security.csrf.CrumbFilter doFilterWARNING: No valid crumb was included in request for /job/##jobname##/build. Returning 403.So I guess a crumb/token needs to be posted with the request - in the case where CSRF protection is enabled.e.g. "Remote access with CSRF protection enabled" describes how to do it on command-linehttps://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console= test latest plugin built from source: works if CSRF Protection is disabled =I suppose I could disable CSRF Protection . . . yes, it works if CSRF Protection is disabled. :) https://wiki.jenkins-ci.org/display/JENKINS/CSRF+ProtectionOct 05, 2016 12:29:06 PM hudson.model.Run executeINFO: publish_system_test_regression_README_to_jenkins #101 main build action completed: SUCCESS= test latest plugin released: problem reproduced "plugin offered a GET link" =Earlier I reproduced the problem described on this bug with latest available Schedule Build Plugin.I installed Schedule Build Plugin yesterday (Wed Oct 4th). Version 0.3.4 (release dated 16 Sep 2015).Icons for Schedule Build appear okay if build scheduled I got a warning "plugin offered a GET link" as reported on this bug.There did appear to be some sort of a job scheduled and it said it "expires in Xhr/min. Waiting for Ymin/hr." which was correct for the time I scheduled. BUT It did not run the job. :-( I couldn't find anything relevant in logs.Url, presumably the GET:http://jenkins:/job/jobname/build?delay=47212secI'm using Jenkins 2.2http://stackoverflow.com/questions/35029486/how-can-i-schedule-a-job-to-run-in-the-future-but-only-one-time-ever/39858002#39858002 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-28961) GET/POST with schedule-build-plugin
Title: Message Title James Coleman edited a comment on JENKINS-28961 Re: GET/POST with schedule-build-plugin Thanks for working on a fix for this!Confirmed fixed BUT needed to disable CSRF Protection to get it to work. :P= test latest plugin built from source: problem if CSRF Protection is enabled =When attempting to schedule a job it fails (quietly) and I get this in jenkins log:Oct 05, 2016 12:13:32 PM hudson.security.csrf.CrumbFilter doFilterWARNING: No valid crumb was included in request for /job/##jobname##/build. Returning 403.So I guess a crumb/token needs to be posted with the request - in the case where CSRF protection is enabled.e.g. "Remote access with CSRF protection enabled" describes how to do it on command-linehttps://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console= test latest plugin built from source: works if CSRF Protection is disabled =I suppose I could disable CSRF Protection . . . yes, it works if CSRF Protection is disabled. :)https://wiki.jenkins-ci.org/display/JENKINS/CSRF+ProtectionOct 05, 2016 12:29:06 PM hudson.model.Run executeINFO: publish_system_test_regression_README_to_jenkins # #jobname## # 101 main build action completed: SUCCESS= test latest plugin released: problem reproduced "plugin offered a GET link" =Earlier I reproduced the problem described on this bug with latest available Schedule Build Plugin.I installed Schedule Build Plugin yesterday (Wed Oct 4th). Version 0.3.4 (release dated 16 Sep 2015).Icons for Schedule Build appear okay if build scheduled I got a warning "plugin offered a GET link" as reported on this bug.There did appear to be some sort of a job scheduled and it said it "expires in Xhr/min. Waiting for Ymin/hr." which was correct for the time I scheduled. BUT It did not run the job. :-( I couldn't find anything relevant in logs.Url, presumably the GET:http://jenkins:/job/jobname/build?delay=47212secI'm using Jenkins 2.2http://stackoverflow.com/questions/35029486/how-can-i-schedule-a-job-to-run-in-the-future-but-only-one-time-ever/39858002#39858002 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38703) [INFO] Deploying artifact not workign with http forwarding proxy
Title: Message Title Jordi Redondo edited a comment on JENKINS-38703 Re: [INFO] Deploying artifact not workign with http forwarding proxy Hi,As I did read different literature about the proxy usage and results on settings.xml, I tried to test under the below three scenarios (once at time). One scenario with HTTP, other with HTTP+ HTTPS and other with HTTPS only . The target URL I tried to use from Artifactory it is HTTPS. proxies>myhttpproxytruehttpmyhost8080localhostproxies>myhttpproxytruehttpsmyhost8080localhostproxies>myhttpproxytrue*myhost8080localhostOne interesting aspect to remark. I tried to inject to artifactory by command line script section at jenkins job, and it works, but if I try from Artifactory plugin, it simply ignores the proxy and tries to artifact directly bypassing the proxy. 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-38732) Add support for claiming a 'stage' within a pipeline job
Title: Message Title Richard Kettelerij updated an issue Jenkins / JENKINS-38732 Add support for claiming a 'stage' within a pipeline job Change By: Richard Kettelerij The claim plugin currently operates on the job level (i.e. allow claiming of jobs /builds ). This is fine if you have a lot of small freestyle jobs. But with the new pipeline jobs (previously known as workflow jobs) you only have one job for your entire pipeline. The claim plugin already support claiming a failed pipeline job (JENKINS-27206) but this doesn't align with every use case. Since pipeline jobs are made up of stages - and visualized as such by both the Stage View plugin and the new BlueOcean UI - it would ideal if you could claim a certain stage (ie. part of the pipeline).I understand this may not be a trivial change since the concept of a stage isn't (yet?) as fundamental to Jenkins as jobs are. Nevertheless I think to a lot of folks claiming ownership of a failed stage would feel more natural than claiming the entire pipeline run. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38473) Changing the JNLP agent port via Groovy can cause long timeout
Title: Message Title stephenconnolly updated JENKINS-38473 Jenkins / JENKINS-38473 Changing the JNLP agent port via Groovy can cause long timeout Change By: stephenconnolly Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37461) Add support for pipeline in Task Scanner plugin
Title: Message Title Mike . resolved as Fixed Looks like this was implemented back in Release 4.46. I quickly checked on our Jenkins instance and it's working fine. Jenkins / JENKINS-37461 Add support for pipeline in Task Scanner plugin Change By: Mike . 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 m
[JIRA] (JENKINS-38733) NuGet-Plugin build trigger ignores update constrain
Title: Message Title Harm-Torsten Reinke created an issue Jenkins / JENKINS-38733 NuGet-Plugin build trigger ignores update constrain Issue Type: Bug Assignee: Unassigned Components: nuget-plugin Created: 2016/Oct/05 12:26 PM Environment: Jenkins ver. 2.7.4 on win7 nuget-plugin 0.6 building a .NET solution (created with VS2015) Priority: Major Reporter: Harm-Torsten Reinke In my project I defined a build trigger on NuGet updates. Whenever the plugin checks for updates it schedules a build because it ignores the allowedVersions attribute in packages.config file (http://docs.nuget.org/ndocs/consume-packages/reinstalling-and-updating-packages). I would expect no build scheduling if there is no newer version matching my update constrain. Add Comment
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Yury Zaytsev reopened an issue So, in addition to causing massive problems on Windows, this also causes trouble on Unix, if the workspace contains shell scripts which use binaries residing in the workspace as interpreters. That is, something like what follows: $ cat foo #!/home/jenkins/agent/workspace/xxx-O7T6IFSVMNBO5RYGRVNFUGEOPAZAIQ4GQRK47UUDIOZMEN3K2OAA/source/lib/python-san/install/bin/python-dbg One might think this ought to happen very rarely, but that's not the case! Basically, when you install any Python modules in a local prefix tree, it hardcodes the absolute path to the interpreter into the scripts and are you are screwed See here for the details on `#!` maximum length limits (127 bytes on Linux): http://www.in-ulm.de/~mascheck/various/shebang/ Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Yury Zaytsev Resolution: Fixed Status: Resolved Reopened Add Comment
[JIRA] (JENKINS-38680) Report better cfg. issues
Title: Message Title Pavel Janoušek commented on JENKINS-38680 Re: Report better cfg. issues PR sent. 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-38680) Report better cfg. issues
Title: Message Title Pavel Janoušek started work on JENKINS-38680 Change By: Pavel Janoušek 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-38673) Update dependencies of plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38673 Re: Update dependencies of plugins Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/log-karaoke/freestyle.js src/test/resources/test_scripts/freestyle.sh http://jenkins-ci.org/commit/blueocean-acceptance-test/a21c0de4c41f719737864907d9309e6b34042182 Log: JENKINS-38673 update tests to run more stable (#56) 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-38367) More descriptive ERROR log msg in ForemanSharedNodeCloud
Title: Message Title Pavel Janoušek commented on JENKINS-38367 Re: More descriptive ERROR log msg in ForemanSharedNodeCloud PR sent. 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-38367) More descriptive ERROR log messages
Title: Message Title Pavel Janoušek updated an issue Jenkins / JENKINS-38367 More descriptive ERROR log messages Change By: Pavel Janoušek Summary: More descriptive ERROR log msg in ForemanSharedNodeCloud messages 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-38367) More descriptive ERROR log messages
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-38367
More descriptive ERROR log messages
Change By:
Pavel Janoušek
If an unhandled exception is thrown in {{provision(label, excessWorkload)}} the code it isn't clear where and how it [occurred|https://github occur . com/pjanouse/foreman-node-sharing-plugin/blob/master/src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java#L187], so we We should add a more descriptive message (and print stacktrace stack trace is very welcome)
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-28961) GET/POST with schedule-build-plugin
Title: Message Title James Coleman commented on JENKINS-28961 Re: GET/POST with schedule-build-plugin Upgrading to jenkins 2.7.4 solved the problem for me with CSRF Protection. I have now CSRF Protection enabled and Schedule Build Plugin from latest source on github working. 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-38367) More descriptive ERROR log messages
Title: Message Title Pavel Janoušek updated an issue Jenkins / JENKINS-38367 More descriptive ERROR log messages Change By: Pavel Janoušek If an unhandled exception is thrown in the code it isn't clear where and how it occur occurred . We should add a more descriptive message (and print stack trace is very welcome) 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-36133) Animate in steps when stage node is clicked
Title: Message Title Thorsten Scherler updated JENKINS-36133 Jenkins / JENKINS-36133 Animate in steps when stage node is clicked Change By: Thorsten Scherler 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-38734) RTC environment variables to set
Title: Message Title Fabian Güttge created an issue Jenkins / JENKINS-38734 RTC environment variables to set Issue Type: Bug Assignee: Deluan Quintão Components: pipeline, rtc-plugin Created: 2016/Oct/05 1:15 PM Environment: Jenkins: 2.7.2 Pipeline: 2.4 Pipeline Groovy: 2.18 Labels: pipeline jenkins rtc groovy Priority: Minor Reporter: Fabian Güttge When updating the pipeline groovy plugin from 2.17 to 2.18 some RTC related variables e.g. env.team_scm_snapshotUUID and env.team_scm_fetchDestination return null after checking out from RTC by using a build definition. The expected behavior is that these variables return the same values as in the previous version. Add Comment
[JIRA] (JENKINS-38727) FindBugs does not collects analysis results
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-38727 FindBugs does not collects analysis results Change By: Ulli Hafner 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-29414) pmd-plugin and checkstyle-plugin analysis doesn't work when using pmd:check
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-29414 pmd-plugin and checkstyle-plugin analysis doesn't work when using pmd:check Change By: Ulli Hafner Component/s: findbugs-plugin Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38728) FindBugs fails to load SaxParser
Title: Message Title Ulli Hafner commented on JENKINS-38728 Re: FindBugs fails to load SaxParser Is Jenkins running in a container? Did you change some xerces libraries in the bootstrap folders of your installation? 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-38735) OwnershipPluginTest failing against for 2.x versions
Title: Message Title Armando Fernandez created an issue Jenkins / JENKINS-38735 OwnershipPluginTest failing against for 2.x versions Issue Type: Improvement Assignee: Armando Fernandez Components: acceptance-test-harness Created: 2016/Oct/05 1:24 PM Priority: Minor Reporter: Armando Fernandez Some tests in OwnershipPluginTest are failing if run against 2.x wars. Failed tests: OwnershipPluginTest.explicitly_set_ownership:49 Expected: Item owned by jenkins-acceptance-tests-user but: was "http://127.0.0.1:63310/computer/spontaneous_distortion/" " jenkins-acceptance-tests-user | log out\n ENABLE AUTO REFRESH\nJenkins\nNodes\nspontaneous_distortion\n Back to List\n Status\n Delete Agent\n Configure\n Build History\n Load Statistics\n Script Console\n Log\n System Information\n Disconnect\n Manage Ownership\nBuild Executor Status\n1 Idle\nMark this node temporarily offline\nAgent spontaneous_distortion\nNode Owners\nPrimary\njenkins-acceptance-tests-user \nE-mail to Node owners E-mail to Service owners\nProjects tied to spontaneous_distortion\nNone\nPage generated: Oct 5, 2016 3:21:48 PM CESTREST APIJenkins ver. 2.19.1" OwnershipPluginTest.implicitly_set_job_ownership:73 Expected: Item owned by jenkins-acceptance-tests-user but: was "http://127.0.0.1:63583/job/flawed_person/" " jenkins-acceptance-tests-user | log out\n ENABLE AUTO REFRESH\nJenkins\nflawed_person\n Back to Dashboard\n Status\n Changes\n Workspace\n Build Now\n Delete Project\n Configure\n Move\n Manage Ownership\ntrend\nBuild History\nx\n RSS for all RSS for failures\nProject flawed_person\nadd description\nJob Owners\nPrimary\njenkins-acceptance-tests-user \nE-mail to Job owners E-mail to Service owners\nDisable Project\nWorkspace\nRecent Changes\nPermalinks\nPage generated: Oct 5, 2016 3:22:28 PM CESTREST APIJenki
[JIRA] (JENKINS-38735) OwnershipPluginTest failing against for 2.x versions
Title: Message Title Armando Fernandez started work on JENKINS-38735 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-38680) Report better cfg. issues
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38680 Re: Report better cfg. issues Code changed in jenkins User: Scott Hebert Path: src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java src/main/resources/com/redhat/foreman/Messages.properties http://jenkins-ci.org/commit/foreman-node-sharing-plugin/f7471b6fd8ba44bca3626043d2158b932087b81b Log: Merge pull request #11 from pjanouse/JENKINS-38680 JENKINS-38680 More descriptive error messages Compare: https://github.com/jenkinsci/foreman-node-sharing-plugin/compare/64b5e2049058...f7471b6fd8ba 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-38728) FindBugs fails to load SaxParser
Title: Message Title Waldemar Prabucki commented on JENKINS-38728 Re: FindBugs fails to load SaxParser Jenkins is runing inside of apache-tomcat-7.0.39. No libraries hvae been adopted. Just thrwon in a jenkins.war. As long as I know apache is also standard installation. 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-38680) Report better cfg. issues
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38680 Re: Report better cfg. issues Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java src/main/resources/com/redhat/foreman/Messages.properties http://jenkins-ci.org/commit/foreman-node-sharing-plugin/dc4a402044f8b5c6bfec118479489756731280fb Log: JENKINS-38680 More descriptive error messages 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-38367) More descriptive ERROR log messages
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38367 Re: More descriptive ERROR log messages Code changed in jenkins User: Scott Hebert Path: src/main/java/com/redhat/foreman/ForemanAPI.java src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/e5282c1f6f529cbaf7fc4c002327b4469ded6af4 Log: Merge pull request #12 from pjanouse/JENKINS-38367 JENKINS-38367 Be more descriptive when an unhandled exception occurred Compare: https://github.com/jenkinsci/foreman-node-sharing-plugin/compare/f7471b6fd8ba...e5282c1f6f52 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-38564) API to convert json step blob to step syntax (and back) - one step at a time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38564 Re: API to convert json step blob to step syntax (and back) - one step at a time Code changed in jenkins User: Robert Sandell Path: src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterAction.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterActionStepsTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/fcf9a65208eeac6b919c86444b8145855017ef90 Log: JENKINS-38564 Always return an array from toJson 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-38564) API to convert json step blob to step syntax (and back) - one step at a time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38564 Re: API to convert json step blob to step syntax (and back) - one step at a time Code changed in jenkins User: Robert Sandell Path: src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterAction.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/eb24b8970afe13a318fbbf715971426aeef6af46 Log: JENKINS-38564 One findbugs NPD warning fixed Compare: https://github.com/jenkinsci/pipeline-model-definition-plugin/compare/b4682fcbc778...eb24b8970afe 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-38367) More descriptive ERROR log messages
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38367 Re: More descriptive ERROR log messages Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanAPI.java src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/f4f2c774190f24a75ac5bff07b0f13d2d2e58cc5 Log: JENKINS-38367 Be more descriptive when an unhandled exception occurred 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-38680) Report better cfg. issues
Title: Message Title Pavel Janoušek resolved as Fixed Merged. Jenkins / JENKINS-38680 Report better cfg. issues Change By: Pavel Janoušek 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Frieder Rick commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json I had success with a little change in the version from Christian Eichenberger . Check: https://github.com/entfrickler/bitbucket-plugin/commit/eebf4b583fd7c1f75a88eb724f8e3f6ee44a3846 I had no luck with the actual develop branch. I'm running Bitbucket Server v4.3.2 with latest "Post-Receive WebHooks" Plugin https://confluence.atlassian.com/bitbucketserver/post-service-webhook-for-bitbucket-server-776640367.html Jenkins 2.7.4 But would be nice when the Bitbucket Server will be supported by the main plugin in the future. Is there another open ticket for this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38550) "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist
Title: Message Title Jesse Glick updated JENKINS-38550 Jenkins / JENKINS-38550 "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38367) More descriptive ERROR log messages
Title: Message Title Pavel Janoušek resolved as Fixed Merged. Jenkins / JENKINS-38367 More descriptive ERROR log messages Change By: Pavel Janoušek 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-35367) EMail-Ext Extended Pipeline Support - Templates
Title: Message Title Faheem Nadeem commented on JENKINS-35367 Re: EMail-Ext Extended Pipeline Support - Templates Is their an example on how to use tokens? 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-38736) update guice to release version
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-38736 update guice to release version Issue Type: Improvement Assignee: Kanstantsin Shautsou Components: core Created: 2016/Oct/05 1:45 PM Priority: Minor Reporter: Kanstantsin Shautsou beta version was added because of java8 support. beta5 was reverted because of some bug. From all this time appeared released version that fixes random errors caused by beta (can't provide stacktraces now). Add Comment This message was
[JIRA] (JENKINS-38736) update guice to release version
Title: Message Title Jesse Glick started work on JENKINS-38736 Change By: Jesse Glick 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-38736) update guice to release version
Title: Message Title Jesse Glick updated JENKINS-38736 Jenkins / JENKINS-38736 update guice to release version Change By: Jesse Glick 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-38727) FindBugs does not collects analysis results
Title: Message Title Waldemar Prabucki commented on JENKINS-38727 Re: FindBugs does not collects analysis results Only minro? I would say it preety much questions the sense of installing the plugin if it is unable to parse the results. Also makes the analysis of errors much harder. I have attached the file with result findbugsXml.xml which was not parsed correctly. 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-38727) FindBugs does not collects analysis results
Title: Message Title Waldemar Prabucki updated an issue Jenkins / JENKINS-38727 FindBugs does not collects analysis results Change By: Waldemar Prabucki Attachment: findbugsXml.xml 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Frieder Rick reopened an issue Bug is still present in Version 1.5.0 Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Frieder Rick Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/opt
[JIRA] (JENKINS-33622) Classic job configuration page shown for Multibranch projects
Title: Message Title Jesse Glick assigned an issue to Matthew DeTullio Jenkins / JENKINS-33622 Classic job configuration page shown for Multibranch projects Change By: Jesse Glick Assignee: Jesse Glick Matthew DeTullio 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-25363) SiteMonitor plugin doesn't seem to honor proxy settings
Title: Message Title Francisco Hernandez Suarez started work on JENKINS-25363 Change By: Francisco Hernandez Suarez 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-33622) Classic job configuration page shown for Multibranch projects
Title: Message Title Jesse Glick started work on JENKINS-33622 Change By: Jesse Glick 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-25363) SiteMonitor plugin doesn't seem to honor proxy settings
Title: Message Title Francisco Hernandez Suarez assigned an issue to Francisco Hernandez Suarez Jenkins / JENKINS-25363 SiteMonitor plugin doesn't seem to honor proxy settings Change By: Francisco Hernandez Suarez Assignee: cliffano Francisco Hernandez Suarez 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.
