[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success
[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159891#comment-159891 ] SCM/JIRA link daemon commented on JENKINS-12881: Code changed in jenkins User: Joe Hansche Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly gerrithudsontrigger/src/main/webapp/trigger/help-BuildUnsuccessfulFilepath.html gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/DuplicatesUtil.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/6b28ce0abd571c8f9325df195f462862fed42540 Log: JENKINS-12881: Initial implementation > Allow reading custom build message from a workspace file, in case of > non-success > > > Key: JENKINS-12881 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12881 > Project: Jenkins > Issue Type: New Feature > Components: gerrit-trigger >Affects Versions: current >Reporter: Joe Hansche >Assignee: rsandell > Labels: gerrit > > Some background is discussed here: > https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger?focusedCommentId=59508437#comment-59508437 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success
[
https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159892#comment-159892
]
SCM/JIRA link daemon commented on JENKINS-12881:
Code changed in jenkins
User: Joe Hansche
Path:
gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java
gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java
gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/f79e10be25028ad69a433a82b061ebc1bd6371d2
Log:
JENKINS-12881: Obtain failure message at completed-time.
Resolves a potential race condition when a single job
may be executing multiple times before the change "batch"
status is ready to be reported back to Gerrit.
The test setup is:
* Job-A
- Shell: echo "Starting ${BUILD_TAG}" > error-message.txt
sleep 5
- Shell: echo "Always fails ${BUILD_TAG}" > error-message.txt
sleep 5
exit 1
* Job-B
- Shell: echo "Starting ${BUILD_TAG}" > error-message.txt
sleep 15
- Shell: echo "Never fails ${BUILD_TAG}" > error-message.txt
sleep 15
Job-B will always be the long-pole (30 sec). Job-A will always fail,
hopefully with "Always fails __" as the error-message.
Create 2 commits for review, and push both commits to Gerrit. Both
Job-A builds will run and fail within 20 seconds, before the first
Job-B build is even finished executing.
The test is successful if both review commits contain the correct
"Always fails {TAG}" messages, corresponding to the correct URL.
The test fails if any other string exists in the failure message.
> Allow reading custom build message from a workspace file, in case of
> non-success
>
>
> Key: JENKINS-12881
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12881
> Project: Jenkins
> Issue Type: New Feature
> Components: gerrit-trigger
>Affects Versions: current
>Reporter: Joe Hansche
>Assignee: rsandell
> Labels: gerrit
>
> Some background is discussed here:
> https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger?focusedCommentId=59508437#comment-59508437
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success
[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159896#comment-159896 ] SCM/JIRA link daemon commented on JENKINS-12881: Code changed in jenkins User: Robert Sandell Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly gerrithudsontrigger/src/main/webapp/trigger/help-BuildUnsuccessfulFilepath.html gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListenerTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/DuplicatesUtil.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/81f7aeaa165eead88f4e6c37b1ee2d313c4e8738 Log: Merge pull request #12 from jhansche/JENKINS-12881 JENKINS-12881: Allow reading custom build message from a workspace file, in case of non-success Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/c86949f...81f7aea > Allow reading custom build message from a workspace file, in case of > non-success > > > Key: JENKINS-12881 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12881 > Project: Jenkins > Issue Type: New Feature > Components: gerrit-trigger >Affects Versions: current >Reporter: Joe Hansche >Assignee: rsandell > Labels: gerrit > > Some background is discussed here: > https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger?focusedCommentId=59508437#comment-59508437 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success
[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159893#comment-159893 ] SCM/JIRA link daemon commented on JENKINS-12881: Code changed in jenkins User: Joe Hansche Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/7e4c31972ba20d5b556a8d7f470f6e050998c1b4 Log: JENKINS-12881: Refactor the message retrieval Refactor at which point the message is retrieved, and which class is responsible for doing so. Should be more in line with the original intent of the classes, and not introduce a high degree of coupling. > Allow reading custom build message from a workspace file, in case of > non-success > > > Key: JENKINS-12881 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12881 > Project: Jenkins > Issue Type: New Feature > Components: gerrit-trigger >Affects Versions: current >Reporter: Joe Hansche >Assignee: rsandell > Labels: gerrit > > Some background is discussed here: > https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger?focusedCommentId=59508437#comment-59508437 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success
[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159895#comment-159895 ] SCM/JIRA link daemon commented on JENKINS-12881: Code changed in jenkins User: Joe Hansche Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListenerTest.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/0cec882c6d52162dca2367ffa7e486cb061457a4 Log: JENKINS-12881: Adds unit tests for failure-message feature > Allow reading custom build message from a workspace file, in case of > non-success > > > Key: JENKINS-12881 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12881 > Project: Jenkins > Issue Type: New Feature > Components: gerrit-trigger >Affects Versions: current >Reporter: Joe Hansche >Assignee: rsandell > Labels: gerrit > > Some background is discussed here: > https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger?focusedCommentId=59508437#comment-59508437 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success
[ https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159894#comment-159894 ] SCM/JIRA link daemon commented on JENKINS-12881: Code changed in jenkins User: Joe Hansche Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java gerrithudsontrigger/src/main/webapp/trigger/help-BuildUnsuccessfulFilepath.html http://jenkins-ci.org/commit/gerrit-trigger-plugin/2118649a59a7a3be1b787c650f21c21832ba6869 Log: JENKINS-12881: Fixes per code review comments at pull request #12 > Allow reading custom build message from a workspace file, in case of > non-success > > > Key: JENKINS-12881 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12881 > Project: Jenkins > Issue Type: New Feature > Components: gerrit-trigger >Affects Versions: current >Reporter: Joe Hansche >Assignee: rsandell > Labels: gerrit > > Some background is discussed here: > https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger?focusedCommentId=59508437#comment-59508437 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12988) Improve Groovy help file
vjuranek created JENKINS-12988: -- Summary: Improve Groovy help file Key: JENKINS-12988 URL: https://issues.jenkins-ci.org/browse/JENKINS-12988 Project: Jenkins Issue Type: Improvement Components: groovy Reporter: vjuranek Assignee: vjuranek Priority: Minor It would have helped to mention that the version names had to match in the ? help link in the main and job configs where you enter them. Or maybe even to make the 'default' choice work with the auto-installed copy if you don't find one earlier in PATH. See http://groups.google.com/group/jenkinsci-users/browse_thread/thread/32c367d4a2673528 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12989) Improve behavior of "default" installation
vjuranek created JENKINS-12989: -- Summary: Improve behavior of "default" installation Key: JENKINS-12989 URL: https://issues.jenkins-ci.org/browse/JENKINS-12989 Project: Jenkins Issue Type: Improvement Components: groovy Reporter: vjuranek Assignee: vjuranek Priority: Minor If there is some groovy installation defined in global Jenkins config and selected installation is "default", jenkins behavior should be as follows: * call "groovy" (for backward compatibility) * if previous call fails, select one of the installation defined in global jenkins config and try with it Another possibility is to add some checkbox which would allow user to select default installation from those defined in global jenkins config. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12962) Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159897#comment-159897 ] Thomas Fields commented on JENKINS-12962: - I'm now using version 0.7 but unfortunately the problem still exists. Could you try reproducing this locally? Cheers, Tom. > Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin > --- > > Key: JENKINS-12962 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12962 > Project: Jenkins > Issue Type: Bug > Components: ws-cleanup >Affects Versions: current > Environment: Jenkins 1.452, Win7 >Reporter: Thomas Fields >Assignee: vjuranek > > Hi there, > The Workspace Cleanup Plugin does not play nicely with the Copy To Slave > plugin. Here's a snippet from my console output for my build: > 14:33:23 Deleting project workspace... done > 14:33:23 > 14:33:23 [copy-to-slave] Copying 'Engine/Lib/**/*.lib, Engine/Lib/**/*.pdb, > Engine/Lib/**/*.a', excluding nothing, from > 'file:/c:/JCI/workspace/Expat-Live/CONFIG/Debug/TARGET/GCC/VSVERSION/2008' on > 'hudson.slaves.DumbSlave@720397f7' to > 'file:/C:/JCI/current_build/Expat-Live/CL167206' on the master. > Note how the workspace is deleted before the copy step begins. Can this be > fixed please? I assume deleting a workspace is something you'd always want to > do last. > I'd be happy to test any fixes. > Regards, > Tom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12921) Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error
[ https://issues.jenkins-ci.org/browse/JENKINS-12921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159898#comment-159898 ] Ron K commented on JENKINS-12921: - Many thanks. Actually I had found another possible workaround - set the *Checkout/merge to local branch (optional)* field, located in one of the *Advanced* hideaways, to some arbitrary name. Then use the same name as the value of the branch specifier in *Branches to build*. Regarding the proposed workaround with $GERRIT_PATCHSET_REVISION - isn't it required to remove the newly-created branch (which will be named something like ??edb49a1f6...??), otherwise it stays there, accumulates, and gets rebuilt every time? (saying that after looking at the *Git Build Data*->*Built Branches* information page) > Trigger fails to build with "Null value not allowed as an environment > variable: GIT_BRANCH" error > - > > Key: JENKINS-12921 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12921 > Project: Jenkins > Issue Type: Bug > Components: gerrit-trigger >Affects Versions: current > Environment: Ubuntu server, Jenkins 1.451, Gerrit Trigger 2.4.0, Git > Plugin 1.1.15 >Reporter: Ron K >Assignee: rsandell > > When a build is started by the Gerrit Trigger, it always fails with the error > and > stack track pasted below: > Manually triggered by user admin for Gerrit: http://localhost:8080/79 > Building in workspace /mntf/jenkins/jobs/GerritBuilder/workspace > Checkout:workspace / /mntf/jenkins/jobs/GerritBuilder/workspace - > hudson.remoting.LocalChannel@72cbb9 > Using strategy: Gerrit Trigger > Checkout:workspace / /mntf/jenkins/jobs/GerritBuilder/workspace - > hudson.remoting.LocalChannel@72cbb9 > Fetching changes from 1 remote Git repository > Fetching upstream changes from ssh://jenkins@localhost:29418/myrepo.git > Commencing build of Revision 4514e900f88eb22c7c006aa8b8971f55e08b0324 () > FATAL: Null value not allowed as an environment variable: GIT_BRANCH > java.lang.IllegalArgumentException: Null value not allowed as an environment > variable: GIT_BRANCH > at hudson.EnvVars.put(EnvVars.java:162) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:576) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:465) > at hudson.model.Run.run(Run.java:1409) > at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238) > The configuration of the trigger is along the lines given in Alex Blewitt's > article (http://www.infoq.com/articles/Gerrit-jenkins-hudson). Specifically, > the project and branch are configure as: > Path - ** - Path - ** > Searching the forums, mailing lists, and irc logs did not yield a solution, > so we're assuming it's a bug and not > a config issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12990) Cannot build trunk
Henning Groß created JENKINS-12990: -- Summary: Cannot build trunk Key: JENKINS-12990 URL: https://issues.jenkins-ci.org/browse/JENKINS-12990 Project: Jenkins Issue Type: Bug Components: maven Environment: Ubuntu, OpenJDK, maven2 Reporter: Henning Groß Priority: Blocker I checked out the trunk but cannot build it. It seems people use dependencies that are not yet deployed. When I try and use older versions of the hpi-plugin i get "cannot get checksum". Try and checkout the trunk and delete the corresponding folders in your local maven repo and the build will fail. If those deps get installed by jenkins and therefore the jenkins build succeeds, consider adding "deploy" to the jenkins configuration to enable the community to build, too. Missing: -- 1) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.kohsuke.stapler -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 3) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 4) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 4) org.kohsuke.stapler:stapler-jelly:jar:1.169 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.kohsuke.stapler -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 3) org.kohsuke.stapler:stapler-jelly:jar:1.169 5) org.jvnet.maven-jellydoc-plugin:taglib-xml-writer:jar:1.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin -DartifactId=taglib-xml-writer -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin -DartifactId=taglib-xml-writer -Dversion=1.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 4) org.jvnet.maven-jellydoc-plugin:taglib-xml-writer:jar:1.5 -- 5 requi
[JIRA] (JENKINS-12991) unable to install m2release plugin 0.9.0 or 0.9.1 on Hudson 2.2.0
Radu Cotescu created JENKINS-12991: -- Summary: unable to install m2release plugin 0.9.0 or 0.9.1 on Hudson 2.2.0 Key: JENKINS-12991 URL: https://issues.jenkins-ci.org/browse/JENKINS-12991 Project: Jenkins Issue Type: Bug Components: m2release Environment: Enterprise Linux Enterprise Linux Server release 5.6 (Carthage) Oracle Linux Server release 5.6 Red Hat Enterprise Linux Server release 5.6 (Tikanga) Reporter: Radu Cotescu Assignee: teilo I am unable to install the m2release plugin (0.9.0 or 0.9.1) on top of Hudson 2.2.0 due to the following error: java.lang.NullPointerException at hudson.model.UpdateSite$Plugin.getNeededDependencies(UpdateSite.java:580) at hudson.model.UpdateSite$Plugin.deploy(UpdateSite.java:622) at hudson.PluginManager.doInstall(PluginManager.java:539) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:103) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:167) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:249) at winstone.RequestDispatcher.forward(RequestDispatcher.java:335) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:180) at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:148) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:180) at org.hudsonci.servlets.internal.ServletRegistrationFilterAdapter.doFilter(ServletRegistrationFilterAdapter.java:148) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$
[JIRA] (JENKINS-12992) Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14)
Soumen Trivedi created JENKINS-12992: Summary: Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14) Key: JENKINS-12992 URL: https://issues.jenkins-ci.org/browse/JENKINS-12992 Project: Jenkins Issue Type: Bug Components: ivytrigger Affects Versions: current Environment: Installed Jenkins using rpm Reporter: Soumen Trivedi Priority: Blocker Attachments: ErrorStackTrace-IvyTriggerPlugin.pdf, SystemInfo-IvyTriggerPlugin.pdf We get error when we try to copy an existing job that has IvyTrigger configuration, and press save after performing build configuration (ie. changes to SVN URL, Build Section, etc) changes. Same behavior is observed when the source job (or the job being copied) is either a Free Style Project or Ivy Project. - refer to attachment ErrorStackTrace for complete stack trace of this Status Code: 500 Exception: Stacktrace: java.lang.NullPointerException at org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:90) at org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:30) at org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.start(AbstractTriggerByFullContext.java:31) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:78) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) Work around what we have found is: 1. Disable Ivy trigger plugin in the source job (ie. existing job) 2. Copy the job (ie. while creating a new job using Copy Job functionality on Jenkins UI) 3. Update all configurations and press Save. 4. Update Ivy trigger configuration in the new job and press Save. 5. Enable Ivy trigger configuration on the Source job and press Save. If you have any queries, please email me at soumen.triv...@gmail.com Thanks & Regards Soumen Trivedi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12990) Cannot build trunk
[ https://issues.jenkins-ci.org/browse/JENKINS-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159899#comment-159899 ] Henning Groß commented on JENKINS-12990: my bad. i guess. i was able to build the trunk disabling checksum validation... > Cannot build trunk > -- > > Key: JENKINS-12990 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12990 > Project: Jenkins > Issue Type: Bug > Components: maven > Environment: Ubuntu, OpenJDK, maven2 >Reporter: Henning Groß >Priority: Blocker > > I checked out the trunk but cannot build it. It seems people use dependencies > that are not yet deployed. When I try and use older versions of the > hpi-plugin i get "cannot get checksum". > Try and checkout the trunk and delete the corresponding folders in your local > maven repo and the build will fail. If those deps get installed by jenkins > and therefore the jenkins build succeeds, consider adding "deploy" to the > jenkins configuration to enable the community to build, too. > Missing: > -- > 1) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 > 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > 3) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 > 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > 4) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 > 4) org.kohsuke.stapler:stapler-jelly:jar:1.169 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > 3) org.kohsuke.stapler:stapler-jelly:jar:1.169 > 5) org.jvnet.maven-jellydoc-plugin:taglib-xml-writer:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=taglib-xml-writer -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=taglib-xml
[JIRA] (JENKINS-9676) Cannot publish FindBugs reports from remote node
[ https://issues.jenkins-ci.org/browse/JENKINS-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159900#comment-159900 ] Ulli Hafner commented on JENKINS-9676: -- Is this bug still present? Quite a while ago I upgraded to the new findbugs version 2.0.0. Maybe this version handles fixes that bug. > Cannot publish FindBugs reports from remote node > > > Key: JENKINS-9676 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9676 > Project: Jenkins > Issue Type: Bug > Components: findbugs >Affects Versions: current > Environment: Jenkins 1.409, Linux Slaves - OS: Centos 5.3 & Ubuntu > 10.10 (Slave Client 1.409) >Reporter: Stephen Kinnison >Assignee: Ulli Hafner > > When attempting to publish FindBugs report from a Linux slave, I am receiving > the following exception: > [FINDBUGS] Collecting findbugs analysis files... > ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to > exception > hudson.util.IOException2: remote file operation failed: > /apps/hudson/workspace/MyFindBugsJob at > hudson.remoting.Channel@93e684:my-linux-slave > at hudson.FilePath.act(FilePath.java:752) > at hudson.FilePath.act(FilePath.java:738) > at > hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:135) > at > hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:281) > at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:649) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:625) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:603) > at hudson.model.Build$RunnerImpl.post2(Build.java:161) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:572) > at hudson.model.Run.run(Run.java:1386) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:145) > Caused by: java.io.IOException: Remote call on dev-linbuild01 failed > at hudson.remoting.Channel.call(Channel.java:652) > at hudson.FilePath.act(FilePath.java:745) > ... 13 more > Caused by: java.lang.NoClassDefFoundError: Could not initialize class > edu.umd.cs.findbugs.SortedBugCollection > at > hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:242) > at > hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:196) > at > hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:133) > at > hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:93) > at > hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:197) > at > hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:176) > at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:126) > at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:29) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1956) > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:270) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
[
https://issues.jenkins-ci.org/browse/JENKINS-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159902#comment-159902
]
Sergey Titov commented on JENKINS-12660:
The same issue. Master is 1.451, slave - WinXP.
> Fail to start the windows service when trying to launch slave node
> --
>
> Key: JENKINS-12660
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12660
> Project: Jenkins
> Issue Type: Bug
> Components: slave-setup
>Affects Versions: current
> Environment: Master : Redhat 5
> Slave Node : Win7 x64
>Reporter: Rico ZHANG
>Assignee: Kohsuke Kawaguchi
>
> We used to be able to launch the slave node successfully, but it did not work
> since we upgraded the jenkins to latest version (1.449)
> It doesn't dump any exception to the console, but I captured the output:
> {noformat}
> Connecting to 192.168.160.62
> Checking if Java exists
> java full version "1.7.0-b147"
> Installing the Jenkins slave service
> Copying jenkins-slave.exe
> Copying slave.jar
> Copying jenkins-slave.xml
> Registering the service
> ERROR: Failed to create a service: Status Invalid Service Account
> ...
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5905) Static Analysis graphs should appear after the test results
[ https://issues.jenkins-ci.org/browse/JENKINS-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159903#comment-159903 ] Ulli Hafner commented on JENKINS-5905: -- I think this bug is now fixed when the flexible-publisher plug-in is used to configure the publishers. > Static Analysis graphs should appear after the test results > --- > > Key: JENKINS-5905 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5905 > Project: Jenkins > Issue Type: Improvement > Components: analysis-core, core >Reporter: johnsmart >Assignee: Ulli Hafner >Priority: Minor > Attachments: Screen shot 2010-03-11 at 10.40.56 PM.png, Screen shot > 2010-03-11 at 10.41.23 PM.png > > > When I activate the Static Analysis Collector Plugin > (http://wiki.jenkins-ci.org/display/JENKINS/Analysis+Collector+Plugin), the > graphs are displayed above the unit test results, which masks the unit test > results from immediate view. The test results are more important than the > static analysis, no matter how nice the graphs are, so it would be nice if > the static analysis graphs could be listed underneath the unit test results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9815) Findbugs can not publish reports on Weblogic 10.3.0
[
https://issues.jenkins-ci.org/browse/JENKINS-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159901#comment-159901
]
Ulli Hafner commented on JENKINS-9815:
--
Is this bug still present? Quite a while ago I upgraded to the new findbugs
version 2.0.0. Maybe this version handles fixes that bug.
> Findbugs can not publish reports on Weblogic 10.3.0
> ---
>
> Key: JENKINS-9815
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9815
> Project: Jenkins
> Issue Type: Bug
> Components: findbugs
>Affects Versions: current
> Environment: Deployed as a war in WebLogic 10.3.0.0
>Reporter: Eric Miles
>Assignee: Ulli Hafner
>
> When attempting to publish reports at the end of a build, I get the following
> error on first job exection:
> {noformat}
> [FINDBUGS] Collecting findbugs analysis files...
> FATAL: null
> java.lang.ExceptionInInitializerError
> at
> edu.umd.cs.findbugs.DetectorFactoryCollection.getCoreResource(DetectorFactoryCollection.java:305)
> at
> edu.umd.cs.findbugs.SystemProperties.loadPropertiesFromConfigFile(SystemProperties.java:72)
> at
> edu.umd.cs.findbugs.SystemProperties.(SystemProperties.java:55)
> at
> edu.umd.cs.findbugs.SortedBugCollection.(SortedBugCollection.java:172)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:242)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:196)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:133)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:93)
> at
> hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:224)
> at
> hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:183)
> at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:139)
> at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:30)
> at hudson.FilePath.act(FilePath.java:756)
> at hudson.FilePath.act(FilePath.java:738)
> at
> hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:144)
> at
> hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:309)
> at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
> at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:629)
> at
> hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:608)
> at
> hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:586)
> at hudson.model.Build$RunnerImpl.post2(Build.java:156)
> at
> hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:555)
> at hudson.model.Run.run(Run.java:1386)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:47)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:145)
> Caused by: org.dom4j.InvalidXPathException: Invalid XPath expression:
> '/FindbugsPlugin/@pluginid'. Caused by: org/dom4j/DocumentException
> at org.dom4j.xpath.DefaultXPath.parse(DefaultXPath.java:362)
> at org.dom4j.xpath.DefaultXPath.(DefaultXPath.java:59)
> at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230)
> at org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207)
> at org.dom4j.tree.AbstractNode.valueOf(AbstractNode.java:189)
> at edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:441)
> at edu.umd.cs.findbugs.PluginLoader.loadPlugin(PluginLoader.java:254)
> at
> edu.umd.cs.findbugs.PluginLoader.loadInitialPlugins(PluginLoader.java:1053)
> at edu.umd.cs.findbugs.PluginLoader.(PluginLoader.java:1043)
> at
> edu.umd.cs.findbugs.DetectorFactoryCollection.getCoreResource(DetectorFactoryCollection.java:305)
> at
> edu.umd.cs.findbugs.SystemProperties.loadPropertiesFromConfigFile(SystemProperties.java:72)
> at
> edu.umd.cs.findbugs.SystemProperties.(SystemProperties.java:55)
> at
> edu.umd.cs.findbugs.SortedBugCollection.(SortedBugCollection.java:172)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:242)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:196)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:133)
> at
> hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:93)
> at
> hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:224)
> at
> hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:183)
> at hudson.plugins.an
[JIRA] (JENKINS-5905) Static Analysis graphs should appear after the test results
[ https://issues.jenkins-ci.org/browse/JENKINS-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-5905. -- Resolution: Fixed > Static Analysis graphs should appear after the test results > --- > > Key: JENKINS-5905 > URL: https://issues.jenkins-ci.org/browse/JENKINS-5905 > Project: Jenkins > Issue Type: Improvement > Components: analysis-core, core >Reporter: johnsmart >Assignee: Ulli Hafner >Priority: Minor > Attachments: Screen shot 2010-03-11 at 10.40.56 PM.png, Screen shot > 2010-03-11 at 10.41.23 PM.png > > > When I activate the Static Analysis Collector Plugin > (http://wiki.jenkins-ci.org/display/JENKINS/Analysis+Collector+Plugin), the > graphs are displayed above the unit test results, which masks the unit test > results from immediate view. The test results are more important than the > static analysis, no matter how nice the graphs are, so it would be nice if > the static analysis graphs could be listed underneath the unit test results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
[
https://issues.jenkins-ci.org/browse/JENKINS-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159902#comment-159902
]
Sergey Titov edited comment on JENKINS-12660 at 3/6/12 11:17 AM:
-
The same issue. Master is 1.451, slave - Windows Server 2003.
was (Author: lunatic):
The same issue. Master is 1.451, slave - WinXP.
> Fail to start the windows service when trying to launch slave node
> --
>
> Key: JENKINS-12660
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12660
> Project: Jenkins
> Issue Type: Bug
> Components: slave-setup
>Affects Versions: current
> Environment: Master : Redhat 5
> Slave Node : Win7 x64
>Reporter: Rico ZHANG
>Assignee: Kohsuke Kawaguchi
>
> We used to be able to launch the slave node successfully, but it did not work
> since we upgraded the jenkins to latest version (1.449)
> It doesn't dump any exception to the console, but I captured the output:
> {noformat}
> Connecting to 192.168.160.62
> Checking if Java exists
> java full version "1.7.0-b147"
> Installing the Jenkins slave service
> Copying jenkins-slave.exe
> Copying slave.jar
> Copying jenkins-slave.xml
> Registering the service
> ERROR: Failed to create a service: Status Invalid Service Account
> ...
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10109) Error 404 with Exception: Stacktrace: (none) when trying to access a job as guest (not logged in)
[ https://issues.jenkins-ci.org/browse/JENKINS-10109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159904#comment-159904 ] lacostej commented on JENKINS-10109: Yes! Redirecting to a login form seems like a good solution. > Error 404 with Exception: Stacktrace: (none) when trying to access a job as > guest (not logged in) > - > > Key: JENKINS-10109 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10109 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: jenkins on Windows >Reporter: ssbarnea > > Here is the full result I got when trying to access an url like: > http://jenkins.example.com/job/some-jobname/45/ > Error 404Status > Code: 404Exception: Stacktrace: (none) > Generated by Winstone Servlet Engine > v0.9.10 at Sun Jun 26 23:16:03 PDT 2011 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12993) Propagate relevant SVN user to UI in case of merge conflicts
michaelhuettermann created JENKINS-12993: Summary: Propagate relevant SVN user to UI in case of merge conflicts Key: JENKINS-12993 URL: https://issues.jenkins-ci.org/browse/JENKINS-12993 Project: Jenkins Issue Type: New Feature Components: jigomerge Environment: all Reporter: michaelhuettermann In case of a merge conflict, Jigomerge should propagate the Subversion user to the Jenkins UI whose commit led to the conflict and thus is the person who should address the conflict. The necessary information are available as part of that specific Subversion revision. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12990) Cannot build trunk
[ https://issues.jenkins-ci.org/browse/JENKINS-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159905#comment-159905 ] Henning Groß commented on JENKINS-12990: truth is: is was able to mvn clean. mvn compile would fail on some modules (for my purpose it was ok to exclude them). also i needed to add: net.java.sezpoz sezpoz 1.9 > Cannot build trunk > -- > > Key: JENKINS-12990 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12990 > Project: Jenkins > Issue Type: Bug > Components: maven > Environment: Ubuntu, OpenJDK, maven2 >Reporter: Henning Groß >Priority: Blocker > > I checked out the trunk but cannot build it. It seems people use dependencies > that are not yet deployed. When I try and use older versions of the > hpi-plugin i get "cannot get checksum". > Try and checkout the trunk and delete the corresponding folders in your local > maven repo and the build will fail. If those deps get installed by jenkins > and therefore the jenkins build succeeds, consider adding "deploy" to the > jenkins configuration to enable the community to build, too. > Missing: > -- > 1) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 > 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > 3) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 > 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > 4) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 > 4) org.kohsuke.stapler:stapler-jelly:jar:1.169 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > 3) org.kohsuke.stapler:stapler-jelly:jar:1.169 > 5) org.jvnet.maven-jellydoc-plugin:taglib-xml-writer:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=taglib-xml-writer -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file >
[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue
teetoivo created JENKINS-12994: -- Summary: Quiet period is blocking other jobs in queue Key: JENKINS-12994 URL: https://issues.jenkins-ci.org/browse/JENKINS-12994 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Platform: All, OS: All Reporter: teetoivo Starting from version 1.452, a job in queue waiting for the quiet period to pass is blocking all other jobs that have been queued after it. Example: # Job A has quiet period set to 10 seconds # Job B has quiet period set to 300 seconds # Job C has quiet period set to 100 seconds # Jobs get queued in A-B-C order. # Job A starts executing after 10 seconds # After 100 seconds, status of job C changes to "pending - Waiting for next available executor" even if free executors are available # After 300 seconds both jobs B and C start executing This problem is hardly visible when short quiet periods are used but becomes problematic with longer quiet periods or plugins like Naginator that will increase the quiet period to hours if the builds fail enough. Version 1.451 is the last release where this problem isn't visible. From public releases, at least 1.452 and 1.454 are affected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8059) Subversion Plugin does break native svn command line authentication, credentials missing after rewriting auth cache file
[
https://issues.jenkins-ci.org/browse/JENKINS-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159906#comment-159906
]
Stanislav Kanev commented on JENKINS-8059:
--
I think I found the root of the problem.
The native credentials are overwritten only when you use svn externals.
I tested a ckeckout/update of a project without the svn externals and the
credentials are not overwritten.
Hope that helps to finally resolve this issue, as it is a real blocker and it
is not fixed for more than a year.
> Subversion Plugin does break native svn command line authentication,
> credentials missing after rewriting auth cache file
>
>
> Key: JENKINS-8059
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8059
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Environment: Linux, Ubuntu Hardy and Jaunty, Solaris
>Reporter: tkrah
>Assignee: Kohsuke Kawaguchi
>Priority: Blocker
> Attachments: subversion.hpi
>
>
> Hudson does rewrite the authentication file under
> ${user.home}/.subversion/auth/svn.simple/$file and does not insert
> credentials stuff.
> I am using a custom build which does use the command line client (in addition
> to the normal svn usage of the hudson project) - so the credentials are
> important to be in there. My custom project is broken every time hudson does
> rewrite those authentication cache file from subversion.
> Is it possible to configure hudson not to do this rewrite or to insert those
> credentials when the rewrite does happen?
> The only workaround found is to set the immutable bit (removing write
> privileges is not enough) as root user to the file in question which hudson
> is not able to workaround (which is expected here and good).
> Project does build but the log grows with these exception trace:
> Nov 10, 2010 10:54:47 AM hudson.scm.SubversionSCM$CheckOutTask invoke
> INFO: Failed to estimate the remote time stamp
> org.tmatesoft.svn.core.SVNException: svn: Cannot rename file
> '/home/hudson/.subversion/auth/svn.simple/auth.d17e3535-2c01-0010-81b2-1f57b38e3f1e.tmp'
> to
> '/home/hudson/.subversion/auth/svn.simple/1755861b3f63d264955a25532195c4f8'
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
> at
> org.tmatesoft.svn.core.internal.wc.SVNFileUtil.rename(SVNFileUtil.java:552)
> at
> org.tmatesoft.svn.core.internal.wc.SVNWCProperties.setProperties(SVNWCProperties.java:352)
> at
> org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager$PersistentAuthenticationProvider.saveAuthentication(DefaultSVNAuthenticationManager.java:810)
> at
> org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.acknowledgeAuthentication(DefaultSVNAuthenticationManager.java:276)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:606)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:275)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:263)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:516)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1001)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVRepository.info(DAVRepository.java:724)
> at
> hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:698)
> at
> hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:596)
> at hudson.FilePath.act(FilePath.java:753)
> at hudson.FilePath.act(FilePath.java:735)
> at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:589)
> at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:537)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1119)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
> at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
> at hudson.model.Run.run(Run.java:1324)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:139)
> Of cause it can not rename the file, the immutable bit is set and only the
> root user is able to change this or any process which got the
> CAP_LINUX_IMMUTABLE capability bit set - of cause my hudson process does not
> get
[JIRA] (JENKINS-12995) Specifying custom phing build file does not work
Daniel Sloof created JENKINS-12995: -- Summary: Specifying custom phing build file does not work Key: JENKINS-12995 URL: https://issues.jenkins-ci.org/browse/JENKINS-12995 Project: Jenkins Issue Type: Bug Components: phing Affects Versions: current Environment: root@jenkins:~# lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 10.04.3 LTS Release:10.04 Codename: lucid Reporter: Daniel Sloof Assignee: sogabe Since the release of version 0.10, which properly fixes the issue in specifying that moduleroot should be default directory, I can no longer specify a custom phing build file path. looking for '/var/lib/jenkins/jobs/[SOME_JOB]/workspace/Build/Scripts/build.xml' ... [workspace] $ phing -buildfile build.xml build-all deploy [SOME_PROPERTIES_WERE_OMITTED] Buildfile: build.xml does not exist! This absolute path -does- actually exist, and 'Phing Build File' path is simply 'Build/Scripts/build.xml'. So it looks like it is looking for the file in the right location, but then reverts to using just the filename when executing phing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12995) Specifying custom phing build file does not work
[ https://issues.jenkins-ci.org/browse/JENKINS-12995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Sloof updated JENKINS-12995: --- Description: Since the release of version 0.10, which properly fixes the issue in specifying that moduleroot should be default directory, I can no longer specify a custom phing build file path. looking for '/var/lib/jenkins/jobs/[SOME_JOB]/workspace/Build/Scripts/build.xml' ... [workspace] $ phing -buildfile build.xml build-all deploy [SOME_PROPERTIES_WERE_OMITTED] Buildfile: build.xml does not exist! This absolute path does actually exist, and 'Phing Build File' path is simply 'Build/Scripts/build.xml'. So it looks like it is looking for the file in the right location, but then reverts to using just the filename when executing phing. was: Since the release of version 0.10, which properly fixes the issue in specifying that moduleroot should be default directory, I can no longer specify a custom phing build file path. looking for '/var/lib/jenkins/jobs/[SOME_JOB]/workspace/Build/Scripts/build.xml' ... [workspace] $ phing -buildfile build.xml build-all deploy [SOME_PROPERTIES_WERE_OMITTED] Buildfile: build.xml does not exist! This absolute path -does- actually exist, and 'Phing Build File' path is simply 'Build/Scripts/build.xml'. So it looks like it is looking for the file in the right location, but then reverts to using just the filename when executing phing. > Specifying custom phing build file does not work > > > Key: JENKINS-12995 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12995 > Project: Jenkins > Issue Type: Bug > Components: phing >Affects Versions: current > Environment: root@jenkins:~# lsb_release -a > Distributor ID: Ubuntu > Description: Ubuntu 10.04.3 LTS > Release: 10.04 > Codename: lucid >Reporter: Daniel Sloof >Assignee: sogabe > Labels: jenkins, plugin > > Since the release of version 0.10, which properly fixes the issue in > specifying that moduleroot should be default directory, I can no longer > specify a custom phing build file path. > looking for > '/var/lib/jenkins/jobs/[SOME_JOB]/workspace/Build/Scripts/build.xml' ... > [workspace] $ phing -buildfile build.xml build-all deploy > [SOME_PROPERTIES_WERE_OMITTED] > Buildfile: build.xml does not exist! > This absolute path does actually exist, and 'Phing Build File' path is simply > 'Build/Scripts/build.xml'. So it looks like it is looking for the file in the > right location, but then reverts to using just the filename when executing > phing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12996) accept test results from different plugins
Henning Groß created JENKINS-12996: -- Summary: accept test results from different plugins Key: JENKINS-12996 URL: https://issues.jenkins-ci.org/browse/JENKINS-12996 Project: Jenkins Issue Type: Patch Components: core Reporter: Henning Groß Attachments: adds_mvn-remote-test_plugin.patch, refactoring_of_SurefireArchiver1.patch We have developed this plugin: http://evolvis.org/projects/mvn-remote-test/ and we need the fetched test results to be included in jenkins build. Based on the old code i have attached a patch that simply adds our plugin in the old manner. This patch is called "adds_mvn-remote-test_plugin.patch". As I do not think the code was/is smart that way, i have attached a second patch called "refactoring_of_SurefireArchiver1.patch". It has another approach. If a plugin is not know but specifies a reportDirectory it will still get recognized. This enables people to write plugins that do NOT have to be named explicitly. For backwars compatibility I have retained the old behaviour and kept the hard-coded plugins. As I am having problems building the trunk and running the tests and also dont have the time to test it fully on our ci I have to ask you to review the patch properly before accepting it. I am also not perfectly sure if I have though every case through but it pretty much should work ;) Maybe you can accept "adds_mvn-remote-test_plugin.patch" immediately to enable us to complete our plugin and if you like "refactoring_of_SurefireArchiver1.patch" is my contribution to jenkins code base which you can accept/mopdify/use later. Thanks a lot and keep up the good work! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue
[ https://issues.jenkins-ci.org/browse/JENKINS-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159908#comment-159908 ] mwebber commented on JENKINS-12994: --- I'm seeing this, or something like it, as well. I have also recently installed the "Throttle Concurrent Builds Plugin" and the "Exclusion-Plugin", so initially I though it might be related to that, but this ticket suggests it's a core problem. > Quiet period is blocking other jobs in queue > > > Key: JENKINS-12994 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12994 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: teetoivo > > Starting from version 1.452, a job in queue waiting for the quiet period to > pass is blocking all other jobs that have been queued after it. > Example: > # Job A has quiet period set to 10 seconds > # Job B has quiet period set to 300 seconds > # Job C has quiet period set to 100 seconds > # Jobs get queued in A-B-C order. > # Job A starts executing after 10 seconds > # After 100 seconds, status of job C changes to "pending - Waiting for next > available executor" even if free executors are available > # After 300 seconds both jobs B and C start executing > This problem is hardly visible when short quiet periods are used but becomes > problematic with longer quiet periods or plugins like Naginator that will > increase the quiet period to hours if the builds fail enough. > Version 1.451 is the last release where this problem isn't visible. From > public releases, at least 1.452 and 1.454 are affected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12133) need to use redeploy, or force deploy for glassfish
[
https://issues.jenkins-ci.org/browse/JENKINS-12133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159907#comment-159907
]
Alessandro Oliveira commented on JENKINS-12133:
---
anybody found a workaround for this?
> need to use redeploy, or force deploy for glassfish
> ---
>
> Key: JENKINS-12133
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12133
> Project: Jenkins
> Issue Type: Bug
> Components: deploy
>Reporter: Derek Knapp
>
> After the 1st build I get the following exception
> If I were deploying using the command line, I would simply add --force to the
> command, for example
> {code}
> asadmin deploy --force /root/itrac/itmems4/itmems4-ear/target/itmems4-ear.ear
> {code}
> Simply adding --force to the command should do the trick, as there is no
> negative side effects.
> {code}
> Deploying
> /root/.jenkins/jobs/itmems4/workspace/itmems4-ear/target/itmems4-ear.ear to
> container GlassFish 3.x Remote
> ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to
> exception
> org.codehaus.cargo.util.CargoException: Deployment has failed: Action failed
> Deploying application to target server failed; Error occurred during
> deployment: Application with name itmems4-ear is already registered. Either
> specify that redeployment must be forced, or redeploy the application. Or if
> this is a new deployment, pick a different name. Please see server.log for
> more details.
> at
> org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.waitForProgressObject(AbstractJsr88Deployer.java:220)
> at
> org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.deploy(AbstractJsr88Deployer.java:76)
> at
> org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:142)
> at
> hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:60)
> at
> hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:86)
> at
> hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:73)
> at hudson.FilePath.act(FilePath.java:783)
> at hudson.FilePath.act(FilePath.java:765)
> at
> hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:73)
> at
> hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:45)
> at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
> at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
> at
> hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:1014)
> at
> hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
> at hudson.model.Run.run(Run.java:1429)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:238)
> Finished: FAILURE
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12997) Verson number variable empty when multiple concurrent builds are running
Peter Lillevold created JENKINS-12997:
-
Summary: Verson number variable empty when multiple concurrent
builds are running
Key: JENKINS-12997
URL: https://issues.jenkins-ci.org/browse/JENKINS-12997
Project: Jenkins
Issue Type: Bug
Components: versionnumber
Environment: Jenkins 1.452
Reporter: Peter Lillevold
I have configured a job to generate and use a version number like this:
0.0.${BUILD_NUMBER}.${SVN_REVISION}
and place it in a variable called BUILD_VERSION.
This works nicely when only one build is executing. But if a second build of
the job is started while the first is running, the content of the BUILD_VERSION
variable will be empty for the duration of that build.
This is a major issue for us since it practically means we have to turn of
"Execute concurrent builds if necessary" on all our CI builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Richard Taylor created JENKINS-12998:
Summary: Allows variable subistution for Job 'Restrict where this
project can be run' label expression
Key: JENKINS-12998
URL: https://issues.jenkins-ci.org/browse/JENKINS-12998
Project: Jenkins
Issue Type: New Feature
Components: core
Affects Versions: current
Environment: Windows Server 2008 SP2
Reporter: Richard Taylor
Fix For: current
Allow variable substitution for the 'Restrict where this project can be run'
label expression field of the job configuration.
Substitution of the form ${BRANCH} where BRANCH is a parameter to the job, will
allow the job to run on any node with a label which matches BRANCH.
Motivation.
We have large branches which can take several hours to checkout from fresh. We
therefore need to ensure that jobs are run on slaves which already have the
branch checkedout in order to keep build times at acceptiable levels. Atm we
have some Jobs which we need to be able to run on any branch, these jobs have a
parameter BRANCH which is currently used to by the perforce plugin to set the
correct depot path. Depending on the number of files which needs to be synced
this can cause a significant delay in build times.
The alternative is to duplicate the job and hardcode the node label for each
branch, this solves the re-sync issue but causes duplicated jobs and a
maintiance headache. Not to mention it clutters the interface and confuses the
users.
Having parameter subistution on the node label field would allow us to specify
which slave group to use for which branches and then have Jenkins take care of
all of the management.
Hopefully this is a quick and easy feature to add.
Many thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12999) Cannot delete a "Throttle Concurrent Builds" category
mwebber created JENKINS-12999:
-
Summary: Cannot delete a "Throttle Concurrent Builds" category
Key: JENKINS-12999
URL: https://issues.jenkins-ci.org/browse/JENKINS-12999
Project: Jenkins
Issue Type: Bug
Components: throttle-concurrents
Reporter: mwebber
Assignee: abayer
On the main Jenkins config page, I defined a new category ("Throttle Concurrent
Builds" "Multi-Project Throttle Categories").
The category cannot be deleted. Clicking the delete button appears to remove
it, but if you go back into the config screen, it reppears.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11938) Jenkins loses builds when restarted
[
https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159909#comment-159909
]
Balazs Jantek commented on JENKINS-11938:
-
+1, it also blocks our CI. Jenkins ver. 1.446. It happens only if a specific
ant target is added to the build steps (Selenium tests actually..) Not using
SetEnv and EnvInject plugins.
> Jenkins loses builds when restarted
> ---
>
> Key: JENKINS-11938
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11938
> Project: Jenkins
> Issue Type: Bug
> Components: other, versionnumber
>Affects Versions: current
> Environment: tomcat 7.0.22
> windows server 2008 r2
>Reporter: Ben Dean
>
> Jenkins version 1.437
> If I stop the Apache Tomcat windows service, a bunch of my builds disappear
> from the history of the jobs. The missing builds are still on disk in the
> build folder, it just doesn't "find" them when making the history list.
> The jobs that lose history use the version number plugin and I had recently
> changed the version format from "4.3.${BUILDS_ALL_TIME}" to
> "4.4.${BUILDS_ALL_TIME}". The builds that disappear are all those after I
> changed this format. Also affects jobs that are downstream from those with
> version number changes.
> I could not find any Component related to the build history for a job. If
> someone knows what that should be feel free to change this. Also, sorry if
> there's not enough (or to much) information, this is the first Jenkins bug I
> have filed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12836) Gerrit-Trigger spams log with "class ....Branch is missing its descriptor in ... ....GerritProject.getBranches()"
[
https://issues.jenkins-ci.org/browse/JENKINS-12836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159911#comment-159911
]
SCM/JIRA link daemon commented on JENKINS-12836:
Code changed in jenkins
User: Robert Sandell
Path:
gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/data/Branch.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/dfed6f5b6c27525ebc9df31070e9c06abb49dc9d
Log:
Merge pull request #13 from tbroyer/patch-1
JENKINS-12836: add a Descriptor for the Branch to nuke warning in the logs.
Compare:
https://github.com/jenkinsci/gerrit-trigger-plugin/compare/81f7aea...dfed6f5
> Gerrit-Trigger spams log with "class Branch is missing its descriptor in
> ... GerritProject.getBranches()"
> -
>
> Key: JENKINS-12836
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12836
> Project: Jenkins
> Issue Type: Bug
> Components: gerrit-trigger
> Environment: Jenkins 1.451 with Gerrit-Trigger 2.3.1, then upgraded
> to Gerrit-Trigger 2.4.0.
>Reporter: Thomas Broyer
>Assignee: rsandell
>Priority: Minor
> Attachments: jenkins.log
>
>
> Log is full of:
> {noformat}
> Caused by: java.lang.AssertionError: class
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.data.Branch is
> missing its descriptor in public java.util.List
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.data.GerritProject.getBranches().
> See
> https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+missing+descriptor
> at
> hudson.model.Descriptor$PropertyType.getItemTypeDescriptorOrDie(Descriptor.java:194)
> ... 198 more
> {noformat}
> See attachment for full log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12836) Gerrit-Trigger spams log with "class ....Branch is missing its descriptor in ... ....GerritProject.getBranches()"
[
https://issues.jenkins-ci.org/browse/JENKINS-12836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159910#comment-159910
]
SCM/JIRA link daemon commented on JENKINS-12836:
Code changed in jenkins
User: Thomas Broyer
Path:
gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/data/Branch.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/92dc4dd6878913b8eb9c837bff8ae93e17be324e
Log:
JENKINS-12836: add a Descriptor for the Branch to nuke warning in the logs.
> Gerrit-Trigger spams log with "class Branch is missing its descriptor in
> ... GerritProject.getBranches()"
> -
>
> Key: JENKINS-12836
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12836
> Project: Jenkins
> Issue Type: Bug
> Components: gerrit-trigger
> Environment: Jenkins 1.451 with Gerrit-Trigger 2.3.1, then upgraded
> to Gerrit-Trigger 2.4.0.
>Reporter: Thomas Broyer
>Assignee: rsandell
>Priority: Minor
> Attachments: jenkins.log
>
>
> Log is full of:
> {noformat}
> Caused by: java.lang.AssertionError: class
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.data.Branch is
> missing its descriptor in public java.util.List
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.data.GerritProject.getBranches().
> See
> https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+missing+descriptor
> at
> hudson.model.Descriptor$PropertyType.getItemTypeDescriptorOrDie(Descriptor.java:194)
> ... 198 more
> {noformat}
> See attachment for full log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12997) Verson number variable empty when multiple concurrent builds are running
[
https://issues.jenkins-ci.org/browse/JENKINS-12997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Lillevold updated JENKINS-12997:
--
Component/s: plugin
> Verson number variable empty when multiple concurrent builds are running
>
>
> Key: JENKINS-12997
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12997
> Project: Jenkins
> Issue Type: Bug
> Components: plugin, versionnumber
> Environment: Jenkins 1.452
>Reporter: Peter Lillevold
> Labels: build, concurrent-build
>
> I have configured a job to generate and use a version number like this:
> 0.0.${BUILD_NUMBER}.${SVN_REVISION}
> and place it in a variable called BUILD_VERSION.
> This works nicely when only one build is executing. But if a second build of
> the job is started while the first is running, the content of the
> BUILD_VERSION variable will be empty for the duration of that build.
> This is a major issue for us since it practically means we have to turn of
> "Execute concurrent builds if necessary" on all our CI builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12983) Redundat syncs when using matrix jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159912#comment-159912 ] Rob Petti commented on JENKINS-12983: - It's already assigned to core, so someone will pick it up from there. I recommend voting on it to give it some more attention. > Redundat syncs when using matrix jobs > - > > Key: JENKINS-12983 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12983 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Jenkins 1.452 >Reporter: Thomas Fields > > Hi, > I originally posted this on the mailing list but the lack of replies forced > me to create this issue. See the post here: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/s1HyARUbfbs > Is there any way the Perforce plugin can be changed so that it doesn't do the > redundant sync? It can be a real performance killer if the view you're > syncing to is particularly large. > Regards, > Tom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13000) Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality
Joerg Schwaerzler created JENKINS-13000: --- Summary: Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality Key: JENKINS-13000 URL: https://issues.jenkins-ci.org/browse/JENKINS-13000 Project: Jenkins Issue Type: Bug Components: git, multiple-scms Affects Versions: current Environment: Jenkins v1.449, Windows7 Reporter: Joerg Schwaerzler Assignee: Nicolas De Loof Just tried to do remote-triggering of some jobs to see whether we can make use of post-receive hooks in our git repositories to trigger our build jobs. However, jenkins did only recognize jobs where git plugin was 'directly' used without using the multiple SCMs plugin. - Any jobs using git plugin within a multiple scms configuration are not found: Using "curl '/git/notifyCommit?url='" we just get (for repositories which are only used within multiple SCMs plugin): No git jobs using repository: - For repositories which are used as well with the stand-alone git plugin we get: "Scheduled polling of " However any job where is used in multiple SCMs config is missing here as well. Hope it's not too complicated to fix this issue... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9757) Cobertura plugin fails maven builds unless workspace is whiped
[ https://issues.jenkins-ci.org/browse/JENKINS-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159913#comment-159913 ] Kai Virkki commented on JENKINS-9757: - I'm also experiencing failing maven builds when using Cobertura and there is an existing workspace. When I clean the workspace, the build works. Sometimes it works with an existing workspace, but rarely. I'm using CloudBees run@cloud. > Cobertura plugin fails maven builds unless workspace is whiped > -- > > Key: JENKINS-9757 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9757 > Project: Jenkins > Issue Type: Bug > Components: cobertura >Affects Versions: current > Environment: Solaris 10, Apache Tomcat Version 6.0.29, jdk1.6.0_21, > Jenkins 1.409, Jenkins Cobertura Plugin 1.2, Maven 3, Maven Cobertura 2.5 >Reporter: Todd Rigertas >Assignee: stephenconnolly >Priority: Critical > > The Jenkins Cobertura plugin will always fail a Maven build if the workspace > is not whiped out prior to the build taking place. Ant builds do not seem to > have this behavior. In my Jenkins server, I have both Ant and Maven builds > that use the Cobertura Jenkins plugin. The Ant builds work fine every time. > The maven builds will ALWAYS fail from the Cobertura plugin if the workspace > is not wiped out prior to the maven build running. The Cobertura Maven > plugin DOES successfully create a report. Yet the Jenkins Cobertura plugin > always thinks the build has failed if the workspace has not been wiped, and > then fails to publish the report. See below Maven output (sanitized): > Started by an SCM change > Updating XXX > U pom.xml > At revision 73 > Found mavenVersion 3.0.2 from file > jar:file:/buildtools/hudson/tools/maven-3.0.2/lib/maven-core-3.0.2.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties > Parsing POMs > [workspace] $ /buildtools/binaries/jdk1.6.0_21/bin/java -cp > /buildtools/hudson/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.1.jar:/buildtools/hudson/tools/maven-3.0.2/boot/plexus-classworlds-2.4.jar > org.jvnet.hudson.maven3.agent.Maven3Main > /buildtools/hudson/tools/maven-3.0.2 > /buildtools/tomcat/webapps/hudson/WEB-INF/lib/remoting-1.409.jar > /buildtools/hudson/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.1.jar > 64028 > <===[HUDSON REMOTING CAPACITY]===>channel started > Executing Maven: -B -f /buildtools/hudson/jobs/XXX/workspace/pom.xml package > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building XXX 2.11.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ XXX > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ XXX --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) > @ XXX --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ > XXX --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.7.1:test (default-test) @ XXX --- > [INFO] Surefire report directory: > /buildtools/hudson/jobs/XXX/workspace/target/surefire-reports > --- > T E S T S > --- > There are no tests to run. > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [JENKINS] Recording test results > [INFO] > [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ XXX --- > [INFO] Building jar: > /buildtools/hudson/jobs/XXX/workspace/target/XXX-2.11.0-SNAPSHOT.jar > mojo forkStarted org.codehaus.mojo:cobertura-maven-plugin:2.5(default) > [JENKINS] cobertura-maven-plugin already configured with xml reports enabled > forkedProjectStarted XXX2.11.0-SNAPSHOT > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ XXX > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ XXX --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- cobertura-maven-plugin:2.5:instrument (default) @ XXX --- > [INFO] Cobertura 1.9.4.1 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file > Cobertura: Loaded infor
[JIRA] (JENKINS-9757) Cobertura plugin fails maven builds unless workspace is whiped
[ https://issues.jenkins-ci.org/browse/JENKINS-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159913#comment-159913 ] Kai Virkki edited comment on JENKINS-9757 at 3/6/12 4:02 PM: - I'm also experiencing failing maven builds when using Cobertura and there is an existing workspace. When I clean the workspace, the build works. Sometimes it works with an existing workspace, but rarely. I'm using CloudBees dev@cloud. was (Author: kaitsu): I'm also experiencing failing maven builds when using Cobertura and there is an existing workspace. When I clean the workspace, the build works. Sometimes it works with an existing workspace, but rarely. I'm using CloudBees run@cloud. > Cobertura plugin fails maven builds unless workspace is whiped > -- > > Key: JENKINS-9757 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9757 > Project: Jenkins > Issue Type: Bug > Components: cobertura >Affects Versions: current > Environment: Solaris 10, Apache Tomcat Version 6.0.29, jdk1.6.0_21, > Jenkins 1.409, Jenkins Cobertura Plugin 1.2, Maven 3, Maven Cobertura 2.5 >Reporter: Todd Rigertas >Assignee: stephenconnolly >Priority: Critical > > The Jenkins Cobertura plugin will always fail a Maven build if the workspace > is not whiped out prior to the build taking place. Ant builds do not seem to > have this behavior. In my Jenkins server, I have both Ant and Maven builds > that use the Cobertura Jenkins plugin. The Ant builds work fine every time. > The maven builds will ALWAYS fail from the Cobertura plugin if the workspace > is not wiped out prior to the maven build running. The Cobertura Maven > plugin DOES successfully create a report. Yet the Jenkins Cobertura plugin > always thinks the build has failed if the workspace has not been wiped, and > then fails to publish the report. See below Maven output (sanitized): > Started by an SCM change > Updating XXX > U pom.xml > At revision 73 > Found mavenVersion 3.0.2 from file > jar:file:/buildtools/hudson/tools/maven-3.0.2/lib/maven-core-3.0.2.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties > Parsing POMs > [workspace] $ /buildtools/binaries/jdk1.6.0_21/bin/java -cp > /buildtools/hudson/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.1.jar:/buildtools/hudson/tools/maven-3.0.2/boot/plexus-classworlds-2.4.jar > org.jvnet.hudson.maven3.agent.Maven3Main > /buildtools/hudson/tools/maven-3.0.2 > /buildtools/tomcat/webapps/hudson/WEB-INF/lib/remoting-1.409.jar > /buildtools/hudson/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.1.jar > 64028 > <===[HUDSON REMOTING CAPACITY]===>channel started > Executing Maven: -B -f /buildtools/hudson/jobs/XXX/workspace/pom.xml package > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building XXX 2.11.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ XXX > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ XXX --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) > @ XXX --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ > XXX --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.7.1:test (default-test) @ XXX --- > [INFO] Surefire report directory: > /buildtools/hudson/jobs/XXX/workspace/target/surefire-reports > --- > T E S T S > --- > There are no tests to run. > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [JENKINS] Recording test results > [INFO] > [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ XXX --- > [INFO] Building jar: > /buildtools/hudson/jobs/XXX/workspace/target/XXX-2.11.0-SNAPSHOT.jar > mojo forkStarted org.codehaus.mojo:cobertura-maven-plugin:2.5(default) > [JENKINS] cobertura-maven-plugin already configured with xml reports enabled > forkedProjectStarted XXX2.11.0-SNAPSHOT > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ XXX > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 res
[JIRA] (JENKINS-9757) Cobertura plugin fails maven builds unless workspace is whiped
[ https://issues.jenkins-ci.org/browse/JENKINS-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159913#comment-159913 ] Kai Virkki edited comment on JENKINS-9757 at 3/6/12 4:06 PM: - I'm also experiencing failing maven builds when using Cobertura and there is an existing workspace. When I clean the workspace, the build works. Sometimes it works with an existing workspace, but rarely. I'm using CloudBees dev@cloud. This is the error that comes to the output: "[JENKINS] Unable to add link to cobertura results" was (Author: kaitsu): I'm also experiencing failing maven builds when using Cobertura and there is an existing workspace. When I clean the workspace, the build works. Sometimes it works with an existing workspace, but rarely. I'm using CloudBees dev@cloud. > Cobertura plugin fails maven builds unless workspace is whiped > -- > > Key: JENKINS-9757 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9757 > Project: Jenkins > Issue Type: Bug > Components: cobertura >Affects Versions: current > Environment: Solaris 10, Apache Tomcat Version 6.0.29, jdk1.6.0_21, > Jenkins 1.409, Jenkins Cobertura Plugin 1.2, Maven 3, Maven Cobertura 2.5 >Reporter: Todd Rigertas >Assignee: stephenconnolly >Priority: Critical > > The Jenkins Cobertura plugin will always fail a Maven build if the workspace > is not whiped out prior to the build taking place. Ant builds do not seem to > have this behavior. In my Jenkins server, I have both Ant and Maven builds > that use the Cobertura Jenkins plugin. The Ant builds work fine every time. > The maven builds will ALWAYS fail from the Cobertura plugin if the workspace > is not wiped out prior to the maven build running. The Cobertura Maven > plugin DOES successfully create a report. Yet the Jenkins Cobertura plugin > always thinks the build has failed if the workspace has not been wiped, and > then fails to publish the report. See below Maven output (sanitized): > Started by an SCM change > Updating XXX > U pom.xml > At revision 73 > Found mavenVersion 3.0.2 from file > jar:file:/buildtools/hudson/tools/maven-3.0.2/lib/maven-core-3.0.2.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties > Parsing POMs > [workspace] $ /buildtools/binaries/jdk1.6.0_21/bin/java -cp > /buildtools/hudson/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.1.jar:/buildtools/hudson/tools/maven-3.0.2/boot/plexus-classworlds-2.4.jar > org.jvnet.hudson.maven3.agent.Maven3Main > /buildtools/hudson/tools/maven-3.0.2 > /buildtools/tomcat/webapps/hudson/WEB-INF/lib/remoting-1.409.jar > /buildtools/hudson/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.1.jar > 64028 > <===[HUDSON REMOTING CAPACITY]===>channel started > Executing Maven: -B -f /buildtools/hudson/jobs/XXX/workspace/pom.xml package > [INFO] Scanning for projects... > [INFO] > > [INFO] > > [INFO] Building XXX 2.11.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ XXX > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ XXX --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) > @ XXX --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 0 resource > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ > XXX --- > [INFO] Nothing to compile - all classes are up to date > [INFO] > [INFO] --- maven-surefire-plugin:2.7.1:test (default-test) @ XXX --- > [INFO] Surefire report directory: > /buildtools/hudson/jobs/XXX/workspace/target/surefire-reports > --- > T E S T S > --- > There are no tests to run. > Results : > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [JENKINS] Recording test results > [INFO] > [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ XXX --- > [INFO] Building jar: > /buildtools/hudson/jobs/XXX/workspace/target/XXX-2.11.0-SNAPSHOT.jar > mojo forkStarted org.codehaus.mojo:cobertura-maven-plugin:2.5(default) > [JENKINS] cobertura-maven-plugin already configured with xml reports enabled > forkedProjectStarted XXX2.11.0-SNAPSHOT > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resource
[JIRA] (JENKINS-12505) Automatically install JDK 7 only lists 1 version, is not clear which it is
[ https://issues.jenkins-ci.org/browse/JENKINS-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159915#comment-159915 ] Christian Höltje commented on JENKINS-12505: FYI: The version shown is Java7 (no updates). So 7u1, 7u2, and 7u3 are missing. > Automatically install JDK 7 only lists 1 version, is not clear which it is > -- > > Key: JENKINS-12505 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12505 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current >Reporter: candrews > Attachments: screenshot_008.png > > > In Manage, under JDK, check "Install automatically." Under "Install from > java.sun.com" expand the "version" drop down. > Notice that under Java 6, 5, and 4, the exact version of Java is listed (for > example, 6u29) so you know exactly what version of Java is being referenced. > For Java 7, there is only 1 option: "Java SE Development Kit 7." > There have been 3 version of JDK 7 released so far (7, 7u1, and 7u2) and each > of the updates has fixed important runtime and compile time issues, so > knowing which is used is particularly important. > So which Java 7 is being referenced? And why aren't the other 2 listed? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12505) Automatically install JDK 7 only lists 1 version, is not clear which it is
[ https://issues.jenkins-ci.org/browse/JENKINS-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159914#comment-159914 ] Christian Höltje commented on JENKINS-12505: The problem is that the list http://mirrors.jenkins-ci.org/updates/updates/hudson.tools.JDKInstaller.json is not showing 7u[123]. My understanding is that Oracle changed the layout of their site and the crawler isn't finding the newer Javas. Is there any updates on this? > Automatically install JDK 7 only lists 1 version, is not clear which it is > -- > > Key: JENKINS-12505 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12505 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current >Reporter: candrews > Attachments: screenshot_008.png > > > In Manage, under JDK, check "Install automatically." Under "Install from > java.sun.com" expand the "version" drop down. > Notice that under Java 6, 5, and 4, the exact version of Java is listed (for > example, 6u29) so you know exactly what version of Java is being referenced. > For Java 7, there is only 1 option: "Java SE Development Kit 7." > There have been 3 version of JDK 7 released so far (7, 7u1, and 7u2) and each > of the updates has fixed important runtime and compile time issues, so > knowing which is used is particularly important. > So which Java 7 is being referenced? And why aren't the other 2 listed? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12505) Automatically install JDK 7 only lists 1 version, is not clear which it is
[ https://issues.jenkins-ci.org/browse/JENKINS-12505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159916#comment-159916 ] Tanmay Sinha commented on JENKINS-12505: Are there any updates on this? > Automatically install JDK 7 only lists 1 version, is not clear which it is > -- > > Key: JENKINS-12505 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12505 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current >Reporter: candrews > Attachments: screenshot_008.png > > > In Manage, under JDK, check "Install automatically." Under "Install from > java.sun.com" expand the "version" drop down. > Notice that under Java 6, 5, and 4, the exact version of Java is listed (for > example, 6u29) so you know exactly what version of Java is being referenced. > For Java 7, there is only 1 option: "Java SE Development Kit 7." > There have been 3 version of JDK 7 released so far (7, 7u1, and 7u2) and each > of the updates has fixed important runtime and compile time issues, so > knowing which is used is particularly important. > So which Java 7 is being referenced? And why aren't the other 2 listed? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13001) Use HTTP Proxy Configuration to check for new Jenkins versions
Matt Kraai created JENKINS-13001: Summary: Use HTTP Proxy Configuration to check for new Jenkins versions Key: JENKINS-13001 URL: https://issues.jenkins-ci.org/browse/JENKINS-13001 Project: Jenkins Issue Type: Improvement Components: core Reporter: Matt Kraai Priority: Minor If I configure Jenkins to use my company's HTTP proxy using the Plugin Manager HTTP Proxy Configuration section, Plugin Manager appears to be able to download plugin information, but Jenkins doesn't appear to detect when new versions of Jenkins are released. If I add the appropriate "-Dhttp.proxyHost" option in jenkins.xml, Jenkins does detect when new versions of Jenkins are released. It would be nice if the HTTP Proxy Configuration section was moved to the Jenkins configuration page and used to check for new versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12778) Extend touchstone functionality to allow for multiple touchstones
[ https://issues.jenkins-ci.org/browse/JENKINS-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159917#comment-159917 ] SCM/JIRA link daemon commented on JENKINS-12778: Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html http://jenkins-ci.org/commit/jenkins/7e2500c7d38ccf3b4944013afd11b75aa8c268ea Log: [FIXED JENKINS-12778] this commit and previous 2 commits > Extend touchstone functionality to allow for multiple touchstones > - > > Key: JENKINS-12778 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12778 > Project: Jenkins > Issue Type: New Feature > Components: matrix >Reporter: Thorsten Möllers > Attachments: test_jenkins-12778_jobs.tar, test_jenkins-12778_jobs.tar > > > Since I have to support a constantly/rapidly changing set of branches, each > supporting a couple of platforms, I want to be able to have only one matrix > per branch job to do all builds/tests per branch. To achieve this > efficiently, I need to be able to configure the matrix job to > 1. build main targets for all supported platforms > 2. If 1 succeeds, run unit test for all supported platforms > 3. If 2 succeeds, build additional test tools for more extensive tests > 4. If 3 succeeds, run tests for all supported platforms > For this I need to be able to define different touchstones for each of the > steps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12778) Extend touchstone functionality to allow for multiple touchstones
[ https://issues.jenkins-ci.org/browse/JENKINS-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12778. Resolution: Fixed > Extend touchstone functionality to allow for multiple touchstones > - > > Key: JENKINS-12778 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12778 > Project: Jenkins > Issue Type: New Feature > Components: matrix >Reporter: Thorsten Möllers > Attachments: test_jenkins-12778_jobs.tar, test_jenkins-12778_jobs.tar > > > Since I have to support a constantly/rapidly changing set of branches, each > supporting a couple of platforms, I want to be able to have only one matrix > per branch job to do all builds/tests per branch. To achieve this > efficiently, I need to be able to configure the matrix job to > 1. build main targets for all supported platforms > 2. If 1 succeeds, run unit test for all supported platforms > 3. If 2 succeeds, build additional test tools for more extensive tests > 4. If 3 succeeds, run tests for all supported platforms > For this I need to be able to define different touchstones for each of the > steps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13002) FileNotFoundException when trying to install version 1.22 of analysis collector plugin
keperry created JENKINS-13002: - Summary: FileNotFoundException when trying to install version 1.22 of analysis collector plugin Key: JENKINS-13002 URL: https://issues.jenkins-ci.org/browse/JENKINS-13002 Project: Jenkins Issue Type: Bug Components: analysis-collector, core, update-center Affects Versions: current Environment: Linux - OpenSUSE 11.3, I am using 1.424.3 LTS Jenkins, upgrading from 1.20 to 1.22 for analysis-collector Reporter: keperry Assignee: Ulli Hafner I receive the following error when trying to download the latest analysis-collector plugin: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/plugins/analysis-collector/1.22/analysis-collector.hpi at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1458) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1452) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1106) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:621) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:952) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1060) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:935) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/plugins/analysis-collector/1.22/analysis-collector.hpi at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1401) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2214) at java.net.URLConnection.getHeaderFieldInt(URLConnection.java:596) at java.net.URLConnection.getContentLength(URLConnection.java:491) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:620) ... 9 more Note: I tried switching from the stable update url to the normal, with no avail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12778) Extend touchstone functionality to allow for multiple touchstones
[ https://issues.jenkins-ci.org/browse/JENKINS-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159918#comment-159918 ] dogfood commented on JENKINS-12778: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png! [jenkins_main_trunk #1576|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1576/] [FIXED JENKINS-12778] this commit and previous 2 commits (Revision 7e2500c7d38ccf3b4944013afd11b75aa8c268ea) Result = UNSTABLE Kohsuke Kawaguchi : [7e2500c7d38ccf3b4944013afd11b75aa8c268ea|https://github.com/jenkinsci/jenkins/commit/7e2500c7d38ccf3b4944013afd11b75aa8c268ea] Files : * changelog.html > Extend touchstone functionality to allow for multiple touchstones > - > > Key: JENKINS-12778 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12778 > Project: Jenkins > Issue Type: New Feature > Components: matrix >Reporter: Thorsten Möllers > Attachments: test_jenkins-12778_jobs.tar, test_jenkins-12778_jobs.tar > > > Since I have to support a constantly/rapidly changing set of branches, each > supporting a couple of platforms, I want to be able to have only one matrix > per branch job to do all builds/tests per branch. To achieve this > efficiently, I need to be able to configure the matrix job to > 1. build main targets for all supported platforms > 2. If 1 succeeds, run unit test for all supported platforms > 3. If 2 succeeds, build additional test tools for more extensive tests > 4. If 3 succeeds, run tests for all supported platforms > For this I need to be able to define different touchstones for each of the > steps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10208) "add build step" -> "execute a shell script" doesn't work with IE8
[
https://issues.jenkins-ci.org/browse/JENKINS-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159919#comment-159919
]
Michael Hall commented on JENKINS-10208:
Check to see if you have the "Prevent Cross-site Scripting" protection turned
on in the Jenkins configuration. I had the exact same issue as Robert Baker
described until I disabled the XSS protection. Sounds like an issue but there's
a good work around in the interim. :)
> "add build step" -> "execute a shell script" doesn't work with IE8
> --
>
> Key: JENKINS-10208
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10208
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Environment: IE8 : Version 8.0.6001.18702CO
> Jenkins 1.411
>Reporter: sbernaud
>Priority: Minor
>
> With IE8, in a project config page, nothing happens when I click on "add a
> build step", then "execute a shell script" in the build section of a free
> style project.
> A new text zone should appear, allowing me to write down my shell script.
> The following error appeared :
> {code:title=error message|borderStyle=solid}
> Agent utilisateur : Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2;
> Trident/4.0;
> .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR
> 3.5.30729)
> Horodateur : Mon, 4 Jul 2011 11:26:24 UTC
> Message : Cet objet ne gère pas cette propriété ou cette méthode
> Ligne : 30
> Caractère : 25
> Code : 0
> URI : https://.../adjuncts/1193576e/org/kohsuke/stapler/bind.js
> {code}
> If I activate the javascript debugger the error message is :
> {code:title=error message with debugger|borderStyle=solid}
> Cet objet ne gère pas cette propriété ou cette méthode prototype.js, Ligne
> 1125 Caractère 7
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9507) Synergy "Create a Synergy Baseline" option being listed twice
[ https://issues.jenkins-ci.org/browse/JENKINS-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159920#comment-159920 ] Jeff Chapman commented on JENKINS-9507: --- Which version did this get fixed in? I am on 1.452 and I am seeing this. The Synergy Database section is also duplicated and I have to toggle between the instances per line edited. I can't fill out the whole section at one go. > Synergy "Create a Synergy Baseline" option being listed twice > - > > Key: JENKINS-9507 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9507 > Project: Jenkins > Issue Type: Bug > Components: synergy >Affects Versions: current > Environment: Jenkins 1.408 running Synergy plugin 1.5 on tomcat 5.5.30 >Reporter: pantherse >Assignee: pantherse > Attachments: Picture 1.png > > > It appears that the "Create a Synergy Baseline" option is being listed twice. > Please see the attached screenshot -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann updated JENKINS-12980: --- Affects Version/s: (was: current) Component/s: keyboard-shortcuts (was: www) > With IE8 any page displays a javascript error about sortable.js > --- > > Key: JENKINS-12980 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 > Project: Jenkins > Issue Type: Bug > Components: keyboard-shortcuts > Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, > tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 >Reporter: Alex Lehmann >Priority: Minor > > When accessing Jenkins with IE8, each page displays a javascript error about > sortable.js > Line 242 > Character 9 > Object doesn't support this property or method > Code 0 > http://(host)/jenkins/static/99210c85/scripts/sortable.js > (the text is roughly translated back to English since I do not have an > English Windows to test) > When skipping the error message, the page works, but the error shows up on > any page again. > The same page works on IE6, IE7, IE9 and current Firefox without errors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159921#comment-159921 ] Alex Lehmann commented on JENKINS-12980: After further analysis of the problem, the error is triggered by installation of the keyboard-shortcut plugin 1.0, probably related to the prototype version. When installing a trunk build of the plugin 1.1-SNAPSHOT, it works again. > With IE8 any page displays a javascript error about sortable.js > --- > > Key: JENKINS-12980 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 > Project: Jenkins > Issue Type: Bug > Components: keyboard-shortcuts > Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, > tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 >Reporter: Alex Lehmann >Priority: Minor > > When accessing Jenkins with IE8, each page displays a javascript error about > sortable.js > Line 242 > Character 9 > Object doesn't support this property or method > Code 0 > http://(host)/jenkins/static/99210c85/scripts/sortable.js > (the text is roughly translated back to English since I do not have an > English Windows to test) > When skipping the error message, the page works, but the error shows up on > any page again. > The same page works on IE6, IE7, IE9 and current Firefox without errors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann resolved JENKINS-12980. Resolution: Fixed probably fixed with commit 79cdfd2169e3015883b914febcd3d064d821cd8d > With IE8 any page displays a javascript error about sortable.js > --- > > Key: JENKINS-12980 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 > Project: Jenkins > Issue Type: Bug > Components: keyboard-shortcuts > Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, > tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 >Reporter: Alex Lehmann >Priority: Minor > > When accessing Jenkins with IE8, each page displays a javascript error about > sortable.js > Line 242 > Character 9 > Object doesn't support this property or method > Code 0 > http://(host)/jenkins/static/99210c85/scripts/sortable.js > (the text is roughly translated back to English since I do not have an > English Windows to test) > When skipping the error message, the page works, but the error shows up on > any page again. > The same page works on IE6, IE7, IE9 and current Firefox without errors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3575) authenticated users can modify their own scores
[ https://issues.jenkins-ci.org/browse/JENKINS-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159923#comment-159923 ] SCM/JIRA link daemon commented on JENKINS-3575: --- Code changed in jenkins User: Adrien Lecharpentier Path: src/main/resources/hudson/plugins/cigame/UserScoreProperty/config.jelly http://jenkins-ci.org/commit/ci-game-plugin/009867469070527811cde3d6c668d798ecd0ee01 Log: [JENKINS-3575] users should not be able to change their own score > authenticated users can modify their own scores > --- > > Key: JENKINS-3575 > URL: https://issues.jenkins-ci.org/browse/JENKINS-3575 > Project: Jenkins > Issue Type: Bug > Components: ci-game >Affects Versions: current > Environment: Platform: All, OS: Windows 2000 >Reporter: pathsny >Assignee: redsolo > > In the CI game at the moment users seem to be able to modify their own scores > on > the CI game. If it makes any difference, at the moment users here authenticate > using the active directory plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3575) authenticated users can modify their own scores
[ https://issues.jenkins-ci.org/browse/JENKINS-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159924#comment-159924 ] SCM/JIRA link daemon commented on JENKINS-3575: --- Code changed in jenkins User: Olivier Lamy Path: src/main/resources/hudson/plugins/cigame/UserScoreProperty/config.jelly http://jenkins-ci.org/commit/ci-game-plugin/13a66b77ff9e0719381cb70abacdf4c5505ac1f2 Log: Merge pull request #3 from alecharp/JENKINS-3575 [JENKINS-3575] users should not be able to change their own score Compare: https://github.com/jenkinsci/ci-game-plugin/compare/17268da...13a66b7 > authenticated users can modify their own scores > --- > > Key: JENKINS-3575 > URL: https://issues.jenkins-ci.org/browse/JENKINS-3575 > Project: Jenkins > Issue Type: Bug > Components: ci-game >Affects Versions: current > Environment: Platform: All, OS: Windows 2000 >Reporter: pathsny >Assignee: redsolo > > In the CI game at the moment users seem to be able to modify their own scores > on > the CI game. If it makes any difference, at the moment users here authenticate > using the active directory plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12797) "Don't Keep this build forever" button doesn't work on some matrix job and prevent removing old build
[ https://issues.jenkins-ci.org/browse/JENKINS-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159925#comment-159925 ] Andrew Herron commented on JENKINS-12797: - I'm seeing the same issue, and it's now causing problems after I accidentally built a part of my matrix that was supposed to be excluded by a combination filter. I don't have any builds that are set to keep the logs of artifacts that are fingerprinted, although I used to a long time ago. > "Don't Keep this build forever" button doesn't work on some matrix job and > prevent removing old build > - > > Key: JENKINS-12797 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12797 > Project: Jenkins > Issue Type: Bug > Components: matrix >Reporter: stibbons > > I've several matrix jobs in which I would like to clean old builds, but they > are in a "Keep this build forever" state. > When I click on the "Don't keep this build forever", it doesn't do anything. > In other matrix jobs I can remove the "keep forever" state and then delete > the build, but other no. It ends up taking lot of space ! > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9117) Jenkins hangs in the shutdown mode after thinBackup is triggered
[ https://issues.jenkins-ci.org/browse/JENKINS-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159926#comment-159926 ] Frank Merrow commented on JENKINS-9117: --- Yeah, this is a show stopper for us . . . I cannot have Jenkins shutting itself down. I thought at first perhaps the issue was related to using a UNC path somepath, but mounting the share as a network drive and using x:\somepath didn't help. Account HAS ACCESS to this location, I've browsed there as that user, created and deleted a file. First four settings: X:\Users\hjenkins\March-Web, 30 0 * * *, 10 * * * *, 10 All other settings are blank or unchecked. Note this works fine for me at home no issues . . . the biggest difference at work is that the number of jobs is of course much bigger (over 100) and the number of plugins. Just in case it is a plugin interaction issue . . . plugin info below: Maven 2 Project Plugin Jenkin's Maven 2 project type Warning: This plugin is built for Jenkins 1.452 or newer. It may or may not work in your Jenkins. 1.452 1.450 Static Code Analysis Plug-ins This plug-in provides utilities for the static code analysis plug-ins. 1.381.29 Warnings Plugin This plugin generates the trend report for compiler warnings in the console log or in log files. 3.283.21 Green Balls Changes Hudson to use green balls instead of blue for successful builds 1.111.10 Perforce Plugin Integrates Jenkins with Perforce SCM Repositories. 1.3.9 1.3.8-SNAPSHOT (private-01/23/2012 01:19-gregf) CVS Plugin This bundled plugin integrates Jenkins with CVS version control system. 2.0 1.6 Text-finder Plugin This plugin lets you search keywords in the files you specified and use that to downgrade a "successful" build to be unstable or a failure. 1.9 1.8 Subversion Plugin This plugin adds the Subversion support (via SVNKit) to Jenkins. 1.391.34 Groovy plugin This plugin adds the ability to directly execute Groovy code. 1.111.10 Scriptler Plugin Scriptler allows you to store/edit groovy scripts and execute it on any of the slaves/nodes... no need for copy paste groovy code anymore. > Jenkins hangs in the shutdown mode after thinBackup is triggered > > > Key: JENKINS-9117 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9117 > Project: Jenkins > Issue Type: Bug > Components: thinBackup >Reporter: Thomas Fürer >Assignee: Thomas Fürer > > thinBackup triggers a backup job and did not return from the shutdown mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12992) Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14)
[ https://issues.jenkins-ci.org/browse/JENKINS-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159927#comment-159927 ] gbois commented on JENKINS-12992: - Thanks for your input > Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14) > - > > Key: JENKINS-12992 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12992 > Project: Jenkins > Issue Type: Bug > Components: ivytrigger >Affects Versions: current > Environment: > Installed Jenkins using rpm >Reporter: Soumen Trivedi >Priority: Blocker > Labels: ivy, ivytrigger, jenkins > Attachments: ErrorStackTrace-IvyTriggerPlugin.pdf, > SystemInfo-IvyTriggerPlugin.pdf > > > We get error when we try to copy an existing job that has IvyTrigger > configuration, and press save after performing build configuration (ie. > changes to SVN URL, Build Section, etc) changes. Same behavior is observed > when the source job (or the job being copied) is either a Free Style Project > or Ivy Project. > - refer to attachment ErrorStackTrace for complete stack > trace of this > Status Code: 500 > Exception: > Stacktrace: > java.lang.NullPointerException > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:90) > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:30) > at > org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.start(AbstractTriggerByFullContext.java:31) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:78) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) > Work around what we have found is: > 1. Disable Ivy trigger plugin in the source job (ie. existing job) > 2. Copy the job (ie. while creating a new job using Copy Job functionality on > Jenkins UI) > 3. Update all configurations and press Save. > 4. Update Ivy trigger configuration in the new job and press Save. > 5. Enable Ivy trigger configuration on the Source job and press Save. > If you have any queries, please email me at soumen.triv...@gmail.com > Thanks & Regards > Soumen Trivedi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12992) Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14)
[ https://issues.jenkins-ci.org/browse/JENKINS-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159928#comment-159928 ] SCM/JIRA link daemon commented on JENKINS-12992: Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java src/main/java/org/jenkinsci/lib/xtrigger/AbstractTriggerByFullContext.java http://jenkins-ci.org/commit/xtrigger-lib/3f82eb79f9fc2a68e51e552ec1c7df96555c61f7 Log: Fix JENKINS-12992 > Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14) > - > > Key: JENKINS-12992 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12992 > Project: Jenkins > Issue Type: Bug > Components: ivytrigger >Affects Versions: current > Environment: > Installed Jenkins using rpm >Reporter: Soumen Trivedi >Priority: Blocker > Labels: ivy, ivytrigger, jenkins > Attachments: ErrorStackTrace-IvyTriggerPlugin.pdf, > SystemInfo-IvyTriggerPlugin.pdf > > > We get error when we try to copy an existing job that has IvyTrigger > configuration, and press save after performing build configuration (ie. > changes to SVN URL, Build Section, etc) changes. Same behavior is observed > when the source job (or the job being copied) is either a Free Style Project > or Ivy Project. > - refer to attachment ErrorStackTrace for complete stack > trace of this > Status Code: 500 > Exception: > Stacktrace: > java.lang.NullPointerException > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:90) > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:30) > at > org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.start(AbstractTriggerByFullContext.java:31) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:78) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) > Work around what we have found is: > 1. Disable Ivy trigger plugin in the source job (ie. existing job) > 2. Copy the job (ie. while creating a new job using Copy Job functionality on > Jenkins UI) > 3. Update all configurations and press Save. > 4. Update Ivy trigger configuration in the new job and press Save. > 5. Enable Ivy trigger configuration on the Source job and press Save. > If you have any queries, please email me at soumen.triv...@gmail.com > Thanks & Regards > Soumen Trivedi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12992) Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14)
[ https://issues.jenkins-ci.org/browse/JENKINS-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14) > - > > Key: JENKINS-12992 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12992 > Project: Jenkins > Issue Type: Bug > Components: ivytrigger >Affects Versions: current > Environment: > Installed Jenkins using rpm >Reporter: Soumen Trivedi >Priority: Blocker > Labels: ivy, ivytrigger, jenkins > Attachments: ErrorStackTrace-IvyTriggerPlugin.pdf, > SystemInfo-IvyTriggerPlugin.pdf > > > We get error when we try to copy an existing job that has IvyTrigger > configuration, and press save after performing build configuration (ie. > changes to SVN URL, Build Section, etc) changes. Same behavior is observed > when the source job (or the job being copied) is either a Free Style Project > or Ivy Project. > - refer to attachment ErrorStackTrace for complete stack > trace of this > Status Code: 500 > Exception: > Stacktrace: > java.lang.NullPointerException > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:90) > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:30) > at > org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.start(AbstractTriggerByFullContext.java:31) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:78) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) > Work around what we have found is: > 1. Disable Ivy trigger plugin in the source job (ie. existing job) > 2. Copy the job (ie. while creating a new job using Copy Job functionality on > Jenkins UI) > 3. Update all configurations and press Save. > 4. Update Ivy trigger configuration in the new job and press Save. > 5. Enable Ivy trigger configuration on the Source job and press Save. > If you have any queries, please email me at soumen.triv...@gmail.com > Thanks & Regards > Soumen Trivedi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ
[ https://issues.jenkins-ci.org/browse/JENKINS-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159929#comment-159929 ] Thomas Fields commented on JENKINS-11149: - I am also now hitting this problem. This issue is very old, will it ever get fixed? Thanks Tom > JNLP slave fails to connect if Anonymous has not permission READ > > > Key: JENKINS-11149 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11149 > Project: Jenkins > Issue Type: Bug > Components: slave-setup >Affects Versions: current >Reporter: Matthias Vach >Assignee: Kohsuke Kawaguchi > > Hi all, > I do face a problem with JNLP based windows slaves in combination with > restricted permissions of Anonymous. > If user Anonymous doesn't has READ permission granted, the JNLP slave > (converted to a windows service) fails to connect to the master. > The jenkins-slave.xml contains > > -Xrs -jar "%BASE%\slave.jar" -jnlpUrl > https://xxx:8443/hudson/computer/xxx/slave-agent.jnlp -jnlpCredentials > abcd:efgh -auth abcd:efgh > > The tomcat-users.xml contains > > > > > > > > The jenkins-slave.err.log contains > > Failing to obtain https://xxx:8443/hudson/computer/xxx/slave-agent.jnlp > java.io.IOException: Failed to load > https://xxx:8443/hudson/computer/xxx/slave-agent.jnlp: 500 Internal Server > Error > at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:228) > at hudson.remoting.Launcher.run(Launcher.java:190) > at hudson.remoting.Launcher.main(Launcher.java:166) > Waiting 10 seconds before retry > > The tomcat's localhost.2011-xx-xx.log contains > > SEVERE: Servlet.service() for servlet Stapler threw exception > hudson.security.AccessDeniedException2: anonymous is missing the Read > permission > at hudson.security.ACL.checkPermission(ACL.java:53) > at hudson.model.Node.checkPermission(Node.java:363) > at hudson.model.Hudson.getTarget(Hudson.java:3538) > ... > > The setup is as follows: > > OS: Windows 7 > Tomcat: 6.0.33 > Jenkins: 1.4.10 (also not working with 1.4.31) > JDK: 1.6.27 > Security Realm: Matrix based Security is enabled > Authorization: Delegate to servlet container > permissions of user abcd: Overall Read, Overall Administer > permissions of user Anonymous: none > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9117) Jenkins hangs in the shutdown mode after thinBackup is triggered
[ https://issues.jenkins-ci.org/browse/JENKINS-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159926#comment-159926 ] Frank Merrow edited comment on JENKINS-9117 at 3/6/12 10:11 PM: Yeah, this is a show stopper for us . . . I cannot have Jenkins shutting itself down. I thought at first perhaps the issue was related to using a UNC path somepath, but mounting the share as a network drive and using x:\somepath didn't help. Account HAS ACCESS to this location, I've browsed there as that user, created and deleted a file. (Jenkins itself has yet to write so much as one byte in the specified directory). First four settings: X:\Users\hjenkins\March-Web, 30 0 * * *, 10 * * * *, 10 All other settings are blank or unchecked. Note this works fine for me at home no issues . . . the biggest difference at work is that the number of jobs is of course much bigger (over 100) and the number of plugins. Just in case it is a plugin interaction issue . . . plugin info below: Maven 2 Project Plugin Jenkin's Maven 2 project type Warning: This plugin is built for Jenkins 1.452 or newer. It may or may not work in your Jenkins. 1.452 1.450 Static Code Analysis Plug-ins This plug-in provides utilities for the static code analysis plug-ins. 1.381.29 Warnings Plugin This plugin generates the trend report for compiler warnings in the console log or in log files. 3.283.21 Green Balls Changes Hudson to use green balls instead of blue for successful builds 1.111.10 Perforce Plugin Integrates Jenkins with Perforce SCM Repositories. 1.3.9 1.3.8-SNAPSHOT (private-01/23/2012 01:19-gregf) CVS Plugin This bundled plugin integrates Jenkins with CVS version control system. 2.0 1.6 Text-finder Plugin This plugin lets you search keywords in the files you specified and use that to downgrade a "successful" build to be unstable or a failure. 1.9 1.8 Subversion Plugin This plugin adds the Subversion support (via SVNKit) to Jenkins. 1.391.34 Groovy plugin This plugin adds the ability to directly execute Groovy code. 1.111.10 Scriptler Plugin Scriptler allows you to store/edit groovy scripts and execute it on any of the slaves/nodes... no need for copy paste groovy code anymore. was (Author: fmerrow): Yeah, this is a show stopper for us . . . I cannot have Jenkins shutting itself down. I thought at first perhaps the issue was related to using a UNC path somepath, but mounting the share as a network drive and using x:\somepath didn't help. Account HAS ACCESS to this location, I've browsed there as that user, created and deleted a file. First four settings: X:\Users\hjenkins\March-Web, 30 0 * * *, 10 * * * *, 10 All other settings are blank or unchecked. Note this works fine for me at home no issues . . . the biggest difference at work is that the number of jobs is of course much bigger (over 100) and the number of plugins. Just in case it is a plugin interaction issue . . . plugin info below: Maven 2 Project Plugin Jenkin's Maven 2 project type Warning: This plugin is built for Jenkins 1.452 or newer. It may or may not work in your Jenkins. 1.452 1.450 Static Code Analysis Plug-ins This plug-in provides utilities for the static code analysis plug-ins. 1.381.29 Warnings Plugin This plugin generates the trend report for compiler warnings in the console log or in log files. 3.283.21 Green Balls Changes Hudson to use green balls instead of blue for successful builds 1.111.10 Perforce Plugin Integrates Jenkins with Perforce SCM Repositories. 1.3.9 1.3.8-SNAPSHOT (private-01/23/2012 01:19-gregf) CVS Plugin This bundled plugin integrates Jenkins with CVS version control system. 2.0 1.6 Text-finder Plugin This plugin lets you search keywords in the files you specified and use that to downgrade a "successful" build to be unstable or a failure. 1.9 1.8 Subversion Plugin This plugin adds the Subversion support (via SVNKit) to Jenkins. 1.391.34 Groovy plugin This plugin adds the ability to directly execute Groovy code. 1.111.10 Scriptler Plugin Scriptler allows you to store/edit groovy scripts and execute it on any of the slaves/nodes... no need for copy paste groovy code anymore. > Jenkins hangs in the shutdown mode after thinBackup is triggered > > > Key: JENKINS-9117 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9117 > Project: Jenkins > Issue Type: Bug > Components: thinBackup >Reporter: Thomas Fürer >Assignee: Thomas Fürer > > thinBackup triggers a backup job and did not return fro
[JIRA] (JENKINS-12992) Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14)
[ https://issues.jenkins-ci.org/browse/JENKINS-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159930#comment-159930 ] SCM/JIRA link daemon commented on JENKINS-12992: Code changed in jenkins User: Gregory Boissinot Path: pom.xml http://jenkins-ci.org/commit/ivytrigger-plugin/083dfaa404c58837f014231f5162a2967fc1f72d Log: Fix JENKINS-12992 > Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14) > - > > Key: JENKINS-12992 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12992 > Project: Jenkins > Issue Type: Bug > Components: ivytrigger >Affects Versions: current > Environment: > Installed Jenkins using rpm >Reporter: Soumen Trivedi >Priority: Blocker > Labels: ivy, ivytrigger, jenkins > Attachments: ErrorStackTrace-IvyTriggerPlugin.pdf, > SystemInfo-IvyTriggerPlugin.pdf > > > We get error when we try to copy an existing job that has IvyTrigger > configuration, and press save after performing build configuration (ie. > changes to SVN URL, Build Section, etc) changes. Same behavior is observed > when the source job (or the job being copied) is either a Free Style Project > or Ivy Project. > - refer to attachment ErrorStackTrace for complete stack > trace of this > Status Code: 500 > Exception: > Stacktrace: > java.lang.NullPointerException > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:90) > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:30) > at > org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.start(AbstractTriggerByFullContext.java:31) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:78) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) > Work around what we have found is: > 1. Disable Ivy trigger plugin in the source job (ie. existing job) > 2. Copy the job (ie. while creating a new job using Copy Job functionality on > Jenkins UI) > 3. Update all configurations and press Save. > 4. Update Ivy trigger configuration in the new job and press Save. > 5. Enable Ivy trigger configuration on the Source job and press Save. > If you have any queries, please email me at soumen.triv...@gmail.com > Thanks & Regards > Soumen Trivedi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12992) Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14)
[ https://issues.jenkins-ci.org/browse/JENKINS-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12992. - Assignee: gbois Resolution: Fixed > Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14) > - > > Key: JENKINS-12992 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12992 > Project: Jenkins > Issue Type: Bug > Components: ivytrigger >Affects Versions: current > Environment: > Installed Jenkins using rpm >Reporter: Soumen Trivedi >Assignee: gbois >Priority: Blocker > Labels: ivy, ivytrigger, jenkins > Attachments: ErrorStackTrace-IvyTriggerPlugin.pdf, > SystemInfo-IvyTriggerPlugin.pdf > > > We get error when we try to copy an existing job that has IvyTrigger > configuration, and press save after performing build configuration (ie. > changes to SVN URL, Build Section, etc) changes. Same behavior is observed > when the source job (or the job being copied) is either a Free Style Project > or Ivy Project. > - refer to attachment ErrorStackTrace for complete stack > trace of this > Status Code: 500 > Exception: > Stacktrace: > java.lang.NullPointerException > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:90) > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:30) > at > org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.start(AbstractTriggerByFullContext.java:31) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:78) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) > Work around what we have found is: > 1. Disable Ivy trigger plugin in the source job (ie. existing job) > 2. Copy the job (ie. while creating a new job using Copy Job functionality on > Jenkins UI) > 3. Update all configurations and press Save. > 4. Update Ivy trigger configuration in the new job and press Save. > 5. Enable Ivy trigger configuration on the Source job and press Save. > If you have any queries, please email me at soumen.triv...@gmail.com > Thanks & Regards > Soumen Trivedi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6467) Add a new envrironment varibale to get only the job's name in a matrix project
[ https://issues.jenkins-ci.org/browse/JENKINS-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159931#comment-159931 ] Thomas Fields commented on JENKINS-6467: I'd love this feature as well please. I posted a similar issue a while back but it's even even been assigned yet never mind fixed - https://issues.jenkins-ci.org/browse/JENKINS-9905 > Add a new envrironment varibale to get only the job's name in a matrix project > -- > > Key: JENKINS-6467 > URL: https://issues.jenkins-ci.org/browse/JENKINS-6467 > Project: Jenkins > Issue Type: Improvement > Components: matrix >Affects Versions: current >Reporter: rockeye > > The env var JOB_NAME, and its description in env-vars.html are confusing. > In a simple project, the meaning and the description correspond, but in a > matrix project, it is more complicated. > If the main job's name is Foo, using a matrix with 2 parameters bar and baz, > then JOB_NAME returns "Foo/bar=x,baz=y". This was the request JENKINS-1047. > Is it possible to add another env var, like JOB_SHORT_NAME, or to be more > coherent, use JOB_NAME to get the real name and JOB_IDENTIFIER for example to > get the full description? > Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12992) Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14)
[ https://issues.jenkins-ci.org/browse/JENKINS-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159932#comment-159932 ] Soumen Trivedi commented on JENKINS-12992: -- Thanks alot for this fix and such a quick response. I have tested this new version now it works. thanks once again :) > Error - Job Copy & Saving Configuration when using Ivy Trigger Plugin (v0.14) > - > > Key: JENKINS-12992 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12992 > Project: Jenkins > Issue Type: Bug > Components: ivytrigger >Affects Versions: current > Environment: > Installed Jenkins using rpm >Reporter: Soumen Trivedi >Assignee: gbois >Priority: Blocker > Labels: ivy, ivytrigger, jenkins > Attachments: ErrorStackTrace-IvyTriggerPlugin.pdf, > SystemInfo-IvyTriggerPlugin.pdf > > > We get error when we try to copy an existing job that has IvyTrigger > configuration, and press save after performing build configuration (ie. > changes to SVN URL, Build Section, etc) changes. Same behavior is observed > when the source job (or the job being copied) is either a Free Style Project > or Ivy Project. > - refer to attachment ErrorStackTrace for complete stack > trace of this > Status Code: 500 > Exception: > Stacktrace: > java.lang.NullPointerException > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:90) > at > org.jenkinsci.plugins.ivytrigger.IvyTrigger.getContext(IvyTrigger.java:30) > at > org.jenkinsci.lib.xtrigger.AbstractTriggerByFullContext.start(AbstractTriggerByFullContext.java:31) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:78) > at > org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) > Work around what we have found is: > 1. Disable Ivy trigger plugin in the source job (ie. existing job) > 2. Copy the job (ie. while creating a new job using Copy Job functionality on > Jenkins UI) > 3. Update all configurations and press Save. > 4. Update Ivy trigger configuration in the new job and press Save. > 5. Enable Ivy trigger configuration on the Source job and press Save. > If you have any queries, please email me at soumen.triv...@gmail.com > Thanks & Regards > Soumen Trivedi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12048) Wrong option "--branch" used by change polling
[ https://issues.jenkins-ci.org/browse/JENKINS-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159933#comment-159933 ] Cass Costello edited comment on JENKINS-12048 at 3/6/12 10:46 PM: -- Still exists with Jenkins ver. 1.454 and HG plugin 1.38 Started on Mar 6, 2012 2:43:41 PM [workspace] $ /usr/bin/hg pull --rev default pulling from http://guest:***@f1tst-linbld100/cgi-bin/hgwebdir.cgi/RCALParent/ searching for changes no changes found [workspace] $ /usr/bin/hg log --style /root/.jenkins/jobs/RCALParent/workspace/tmp1653283168161523774style --branch default --no-merges --prune d192aa5a7ebca288cc92070b3e4e7f54578d99fb hg log: option --branch not recognized hg log [OPTION]... [FILE] What's the best way for me to have a look at the code and request a merge? was (Author: cass_costello): Still exists with 1.452 and 1.38 Started on Mar 6, 2012 2:43:41 PM [workspace] $ /usr/bin/hg pull --rev default pulling from http://guest:***@f1tst-linbld100/cgi-bin/hgwebdir.cgi/RCALParent/ searching for changes no changes found [workspace] $ /usr/bin/hg log --style /root/.jenkins/jobs/RCALParent/workspace/tmp1653283168161523774style --branch default --no-merges --prune d192aa5a7ebca288cc92070b3e4e7f54578d99fb hg log: option --branch not recognized hg log [OPTION]... [FILE] What's the best way for me to have a look at the code and request a merge? > Wrong option "--branch" used by change polling > --- > > Key: JENKINS-12048 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12048 > Project: Jenkins > Issue Type: Bug > Components: mercurial >Reporter: Christoph Neuroth >Assignee: davidmc24 >Priority: Critical > > With Jenkins 1.442, Mercurial Plugin 1.38, the change polling issues a "hg > log" command using "\-\-branch foo", which mercurial doesn't know about. > Should be "\-b" or "\-\-only-branch". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12048) Wrong option "--branch" used by change polling
[ https://issues.jenkins-ci.org/browse/JENKINS-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159933#comment-159933 ] Cass Costello commented on JENKINS-12048: - Still exists with 1.452 and 1.38 Started on Mar 6, 2012 2:43:41 PM [workspace] $ /usr/bin/hg pull --rev default pulling from http://guest:***@f1tst-linbld100/cgi-bin/hgwebdir.cgi/RCALParent/ searching for changes no changes found [workspace] $ /usr/bin/hg log --style /root/.jenkins/jobs/RCALParent/workspace/tmp1653283168161523774style --branch default --no-merges --prune d192aa5a7ebca288cc92070b3e4e7f54578d99fb hg log: option --branch not recognized hg log [OPTION]... [FILE] What's the best way for me to have a look at the code and request a merge? > Wrong option "--branch" used by change polling > --- > > Key: JENKINS-12048 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12048 > Project: Jenkins > Issue Type: Bug > Components: mercurial >Reporter: Christoph Neuroth >Assignee: davidmc24 >Priority: Critical > > With Jenkins 1.442, Mercurial Plugin 1.38, the change polling issues a "hg > log" command using "\-\-branch foo", which mercurial doesn't know about. > Should be "\-b" or "\-\-only-branch". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
[ https://issues.jenkins-ci.org/browse/JENKINS-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159934#comment-159934 ] brianharris commented on JENKINS-6817: -- Hi Andrew, given this issue is assigned to you, do you have thoughts on how to evaluate it? Any specific input users can provide to help? > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > -- > > Key: JENKINS-6817 > URL: https://issues.jenkins-ci.org/browse/JENKINS-6817 > Project: Jenkins > Issue Type: Bug > Components: clone-workspace, core >Affects Versions: current >Reporter: nirmal_patel >Assignee: abayer >Priority: Blocker > > I am seeing the same on my Windows XP master-slave setup. I am running latest > Hudson ver. 1.363 > I am using the close-workspace-scm plugin to copy my workspace from master to > slave(150). > Started by user anonymous > Building remotely on 150 > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected > termination of the channel > at hudson.remoting.Request.call(Request.java:137) > at hudson.remoting.Channel.call(Channel.java:555) > at hudson.FilePath.act(FilePath.java:742) > at hudson.FilePath.act(FilePath.java:735) > at hudson.FilePath.unzip(FilePath.java:415) > at > hudson.FileSystemProvisioner$Default$WorkspaceSnapshotImpl.restoreTo(FileSystemProvisioner.java:227) > at > hudson.plugins.cloneworkspace.CloneWorkspaceSCM$Snapshot.restoreTo(CloneWorkspaceSCM.java:344) > at > hudson.plugins.cloneworkspace.CloneWorkspaceSCM.checkout(CloneWorkspaceSCM.java:126) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1044) > at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) > at hudson.model.Run.run(Run.java:1253) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:127) > Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > at hudson.remoting.Request.abort(Request.java:257) > at hudson.remoting.Channel.terminate(Channel.java:602) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:893) > Caused by: java.io.IOException: Unexpected termination of the channel > at hudson.remoting.Channel$ReaderThread.run(Channel.java:875) > Caused by: java.io.EOFException > at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) > at java.io.ObjectInputStream.readObject0(Unknown Source) > at java.io.ObjectInputStream.readObject(Unknown Source) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:869) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12990) Cannot build trunk
[ https://issues.jenkins-ci.org/browse/JENKINS-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159935#comment-159935 ] Kohsuke Kawaguchi commented on JENKINS-12990: - We need to see the part of the Maven output that shows where it tries to download artifacts in question from. They should be all visible from http://repo.jenkins-ci.org/public/ (for example http://repo.jenkins-ci.org/public/org/jenkins-ci/tools/maven-hpi-plugin/1.78/ ) > Cannot build trunk > -- > > Key: JENKINS-12990 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12990 > Project: Jenkins > Issue Type: Bug > Components: maven > Environment: Ubuntu, OpenJDK, maven2 >Reporter: Henning Groß >Priority: Blocker > > I checked out the trunk but cannot build it. It seems people use dependencies > that are not yet deployed. When I try and use older versions of the > hpi-plugin i get "cannot get checksum". > Try and checkout the trunk and delete the corresponding folders in your local > maven repo and the build will fail. If those deps get installed by jenkins > and therefore the jenkins build succeeds, consider adding "deploy" to the > jenkins configuration to enable the community to build, too. > Missing: > -- > 1) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=maven-jellydoc-plugin -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 > 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-groovy -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > 3) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=jellydoc-annotations -Dversion=1.5 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:maven-stapler-plugin:jar:1.16 > 3) org.jvnet.maven-jellydoc-plugin:maven-jellydoc-plugin:jar:1.5 > 4) org.jvnet.maven-jellydoc-plugin:jellydoc-annotations:jar:1.5 > 4) org.kohsuke.stapler:stapler-jelly:jar:1.169 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler > -DartifactId=stapler-jelly -Dversion=1.169 -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.78 > 2) org.kohsuke.stapler:stapler-groovy:jar:1.169 > 3) org.kohsuke.stapler:stapler-jelly:jar:1.169 > 5) org.jvnet.maven-jellydoc-plugin:taglib-xml-writer:jar:1.5 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.jvnet.maven-jellydoc-plugin > -DartifactId=taglib-xml-writer -Dversion=1.5 -Dpackaging=jar > -Dfi
[JIRA] (JENKINS-8694) make all links work with https
[ https://issues.jenkins-ci.org/browse/JENKINS-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159936#comment-159936 ] Pasi Parviainen commented on JENKINS-8694: -- I have somewhat same problem. Every link which does not end with trailing slash fails with error "Your browser (or proxy) sent a request that this server could not understand." For example, after login web browser tries to redirect into http://www.example.com:443/jenkins/ which obviously does not work. Another example https://www.example.com/jenkins/job/MIOVFW/emma redirects into http://www.example.com:443/jenkins/job/MIOVFW/emma/ I have Jenkins behind apache proxy. Connections are made to apache with https, Jenkins serves with plain http. > make all links work with https > -- > > Key: JENKINS-8694 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8694 > Project: Jenkins > Issue Type: Improvement > Components: www >Reporter: Frank Wöckener >Priority: Minor > > Most of the links work well when used behind an SSL enabled proxy (nginx in > our case). Some links are probably hardcoded to http (like the redirect after > login and logout e.g.) so they redirekt to http. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12694) Zentimestamp plugin v3.0 no longer compatible with hudson.
[ https://issues.jenkins-ci.org/browse/JENKINS-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12694. - Resolution: Fixed I'm sorry to not getting back to you sooner. Zentimestamp plugin 3.0 used an extension point available only from Jenkins 1.410. zentimestamp 3.1 is out. In this version, I remove the previous extension point and use another compatible to Hudson 1.392 (before the fork in 1.398). Therefore it is supposed to work. Unfortunately, I didn't have tested. Set issue to fix. Thanks > Zentimestamp plugin v3.0 no longer compatible with hudson. > -- > > Key: JENKINS-12694 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12694 > Project: Jenkins > Issue Type: Bug > Components: zentimestamp >Reporter: Christopher Stephens >Assignee: gbois > > As of version 3.0 the zen timestamp plugin appears to be no longer compatible > with Hudson. I tested it in a stand alone Hudson instance (no additional > plugins) against Hudson versions 2.2.0 and 2.1.0 and noticed that the > BUILD_ID variable is not getting replaced by the correct pattern. > I rolled back to version 2.2 of the plugin which appears to still be > compatible with both versions of Hudson above. > I did not see any errors in the logs when running projects with the plugin > activated, only that the environment variable contained the original > timestamp formatting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11723) appaloosa-plugin allow to deploy only latest binaries from the workspace
[ https://issues.jenkins-ci.org/browse/JENKINS-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159938#comment-159938 ] SCM/JIRA link daemon commented on JENKINS-11723: Code changed in jenkins User: Arnaud Héritier Path: pom.xml src/main/java/org/jenkins/plugins/appaloosa/AppaloosaPublisher.java src/main/java/org/jenkins/plugins/appaloosa/AppaloosaRunListener.java src/main/resources/org/jenkins/plugins/appaloosa/Messages.properties http://jenkins-ci.org/commit/appaloosa-plugin/2dd6f0f9798ebe67d20534022159eece8537b6fd Log: JENKINS-11723 : Add compatibility for the promotion-build plugin. You can now deploy binaries from a previous build and not only the latest one (take care that appaloosa won't allow you to deploy an older version of an application already deployed) > appaloosa-plugin allow to deploy only latest binaries from the workspace > > > Key: JENKINS-11723 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11723 > Project: Jenkins > Issue Type: Improvement > Components: appaloosa > Environment: Affect 1.0 >Reporter: Arnaud Héritier >Assignee: Arnaud Héritier > > The plugin scans the workspace of the build to find binairies and deploy them. > Thus it is impossible to postpone the deployment to a manual step for example > using the promotion plugin for example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11723) appaloosa-plugin allow to deploy only latest binaries from the workspace
[ https://issues.jenkins-ci.org/browse/JENKINS-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159939#comment-159939 ] SCM/JIRA link daemon commented on JENKINS-11723: Code changed in jenkins User: Arnaud Héritier Path: pom.xml http://jenkins-ci.org/commit/appaloosa-plugin/b606b83e3c9a373fd5504eae5e25bafbef162e5c Log: Jump to 1.1 : JENKINS-11723 is a new feature > appaloosa-plugin allow to deploy only latest binaries from the workspace > > > Key: JENKINS-11723 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11723 > Project: Jenkins > Issue Type: Improvement > Components: appaloosa > Environment: Affect 1.0 >Reporter: Arnaud Héritier >Assignee: Arnaud Héritier > > The plugin scans the workspace of the build to find binairies and deploy them. > Thus it is impossible to postpone the deployment to a manual step for example > using the promotion plugin for example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11723) appaloosa-plugin allow to deploy only latest binaries from the workspace
[ https://issues.jenkins-ci.org/browse/JENKINS-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Héritier resolved JENKINS-11723. --- Fix Version/s: current Resolution: Fixed Will be fixed in 1.1 > appaloosa-plugin allow to deploy only latest binaries from the workspace > > > Key: JENKINS-11723 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11723 > Project: Jenkins > Issue Type: Improvement > Components: appaloosa > Environment: Affect 1.0 >Reporter: Arnaud Héritier >Assignee: Arnaud Héritier > Fix For: current > > > The plugin scans the workspace of the build to find binairies and deploy them. > Thus it is impossible to postpone the deployment to a manual step for example > using the promotion plugin for example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9118) When workspace is cloned, symlinks are replaced with copies of the files they point to
[ https://issues.jenkins-ci.org/browse/JENKINS-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159941#comment-159941 ] owenmehegan commented on JENKINS-9118: -- Clone Workspace 0.4, using tar.gz instead of zip, still exhibits this problem :( > When workspace is cloned, symlinks are replaced with copies of the files they > point to > -- > > Key: JENKINS-9118 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9118 > Project: Jenkins > Issue Type: Bug > Components: clone-workspace >Affects Versions: current > Environment: Linux >Reporter: owenmehegan >Assignee: abayer > > When a project uses the "clone workspace for SCM" feature to grab a workspace > from another project, somewhere in that process all symlinks in the original > workspace are replaced with COPIES of the files they are supposed to point > to. These copies are then afflicted with JENKINS-8677, where their exec > permissions are wiped out. I'm pretty sure this is related to the clone > workspace plugin. When I look at the workspace the files are coming FROM, > everything is fine. Then the workspace they end up in, in the job that clones > them, shows this symlink issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12986) "Block build when downstream project is building" and fstrigger problem
[ https://issues.jenkins-ci.org/browse/JENKINS-12986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159942#comment-159942 ] gbois commented on JENKINS-12986: - FSTrigger and its typology XTRigger is not aware about upstream/downstream. XTrigger plugins is aimed at excluding the usage of job dependencies. Could you just upload your job configuration files? I'll try to reproduce it. > "Block build when downstream project is building" and fstrigger problem > --- > > Key: JENKINS-12986 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12986 > Project: Jenkins > Issue Type: Bug > Components: fstrigger >Affects Versions: current > Environment: fstrigger 0.27 > jenkins 1.451 >Reporter: Trevor Baker >Assignee: gbois > > It seems that when you enable "Block build when downstream project is > building" that scheduled polling still occurs. If you use fstrigger and a > poll sees a file change when builds are blocked due to running downstream > jobs, the timestamp or "fingerprint" or the file/folder watched still gets > updated. This means that once the downstream job completes and the block is > removed a new job should be triggered. Currently builds are NOT triggered as > the plugin is comparing the contents observed during the blockout to current > which are the same. > When builds are blocked fstrigger should not update its "state" used for > comparisons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves
[
https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159943#comment-159943
]
SCM/JIRA link daemon commented on JENKINS-12912:
Code changed in jenkins
User: Gregory Boissinot
Path:
pom.xml
http://jenkins-ci.org/commit/urltrigger-plugin/1f783b6f5f60c54e2ae01328504dc79035c69dfd
Log:
Fix JENKINS-12912
> URLTtrigger does not poll on jobs which are tied to disconnected slaves
> ---
>
> Key: JENKINS-12912
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12912
> Project: Jenkins
> Issue Type: Bug
> Components: urltrigger
> Environment: Jenkins 1.451
> URLTrigger Plugin 0.10, 0.14
>Reporter: OHTAKE Tomohiro
>Assignee: gbois
>
> Since 0.10, URLTtrigger does not poll on jobs which are tied to disconnected
> slaves even if there are available executors on master.
> URLTrigger Plugin 0.9 makes master poll the URL even if the jobs are tied to
> slaves.
> If there are changes in URL, a slave that is tied to the job wakes up and
> runs the job.
> URLTrigger 0.9 says that polling has been done on slaves, but master polles.
> {code:title=URLTrigger Log (0.14, job which is tied to disconnected slaves)}
> Polling for the job aa
> Searching a node to run the polling for the label ''.
> Can't find any complete active node for the polling action. Maybe slaves are
> not yet active at this time or the number of executor of the master is 0.
> Checking again in next polling schedule.
> {code}
> {code:title=URLTrigger Log (0.14, job which is not tied to any slaves)}
> Polling for the job bb
> Polling on master.
> Polling started on Feb 28, 2012 10:22:42 AM
> Invoking the url:
> http://aaa.invalid/bb
> Inspecting the content
> Polling complete. Took 0.12 sec.
> No changes.
> {code}
> {code:title=URLTrigger Log (0.9, job which is tied to disconnected slaves)}
> Polling started on Feb 28, 2012 10:51:04 AM
> Searching a node to run the polling for the label ''.
> Invoking the url:
> http://aaa.invalid/bb
> Inspecting the content
> Polling complete. Took 0.14 sec
> No changes.
> {code}
> Workarounds:
> * Downgrade URLTrigger Plugin to 0.9
> * Do not tie jobs which uses Use URLTrigger
> ** Create a job that uses URLTrigger and do not tie the job to any slaves.
> ** Configure the job to build other projects in its post-build actions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves
[
https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-12912.
-
Resolution: Fixed
Please try urlttrigger 0.15 if it suits you
Thanks
> URLTtrigger does not poll on jobs which are tied to disconnected slaves
> ---
>
> Key: JENKINS-12912
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12912
> Project: Jenkins
> Issue Type: Bug
> Components: urltrigger
> Environment: Jenkins 1.451
> URLTrigger Plugin 0.10, 0.14
>Reporter: OHTAKE Tomohiro
>Assignee: gbois
>
> Since 0.10, URLTtrigger does not poll on jobs which are tied to disconnected
> slaves even if there are available executors on master.
> URLTrigger Plugin 0.9 makes master poll the URL even if the jobs are tied to
> slaves.
> If there are changes in URL, a slave that is tied to the job wakes up and
> runs the job.
> URLTrigger 0.9 says that polling has been done on slaves, but master polles.
> {code:title=URLTrigger Log (0.14, job which is tied to disconnected slaves)}
> Polling for the job aa
> Searching a node to run the polling for the label ''.
> Can't find any complete active node for the polling action. Maybe slaves are
> not yet active at this time or the number of executor of the master is 0.
> Checking again in next polling schedule.
> {code}
> {code:title=URLTrigger Log (0.14, job which is not tied to any slaves)}
> Polling for the job bb
> Polling on master.
> Polling started on Feb 28, 2012 10:22:42 AM
> Invoking the url:
> http://aaa.invalid/bb
> Inspecting the content
> Polling complete. Took 0.12 sec.
> No changes.
> {code}
> {code:title=URLTrigger Log (0.9, job which is tied to disconnected slaves)}
> Polling started on Feb 28, 2012 10:51:04 AM
> Searching a node to run the polling for the label ''.
> Invoking the url:
> http://aaa.invalid/bb
> Inspecting the content
> Polling complete. Took 0.14 sec
> No changes.
> {code}
> Workarounds:
> * Downgrade URLTrigger Plugin to 0.9
> * Do not tie jobs which uses Use URLTrigger
> ** Create a job that uses URLTrigger and do not tie the job to any slaves.
> ** Configure the job to build other projects in its post-build actions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13003) pp
Arvind Ramalingam created JENKINS-13003: --- Summary: pp Key: JENKINS-13003 URL: https://issues.jenkins-ci.org/browse/JENKINS-13003 Project: Jenkins Issue Type: Bug Components: job-import, plugin Affects Versions: current Reporter: Arvind Ramalingam Assignee: jieryn Priority: Blocker FAILED - Server returned HTTP response code: 403 when trying to use import plugin to import jobs from one Jenkins to another. It redirects me to the below stack trace. HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: java.lang.NullPointerException org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:603) org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:374) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) org.kohsuke.stapler.Stapler.service(Stapler.java:159) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) root cause java.lang.NullPointerException org.jenkins.ci.plugins.jobimport.JobImportAction.doImport(JobImportAction.java:126) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:616) org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149) org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88) org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:104) org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:374) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) org.kohsuke.stapler.Stapler.service(Stapler.java:159) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.33 logs. Apache Tomcat/6.0.33 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13004) Remove the nonsense configurations in multi-configuration project
Michael Lin created JENKINS-13004: - Summary: Remove the nonsense configurations in multi-configuration project Key: JENKINS-13004 URL: https://issues.jenkins-ci.org/browse/JENKINS-13004 Project: Jenkins Issue Type: Bug Components: multi-slave-config Affects Versions: current Environment: Windows, Mac Reporter: Michael Lin Assignee: rsandell I use Jenkins to configure my multi-configuration project. The Axes I use are: Labels: Mac10.6, Mac10.7, and Windows Platforms: Mac10.6, Mac10.7, WinXP, Win7, and WinServer2008 Tasks: _App_Installer_, _App_Uninstaller_, and so on A matrix will be generated, and I intend to let the tasks from windows platforms go to execute on Windows machines(with Label "Windows"), by using a filter as (label=="Windows"&&(Platforms=="Win7"||Platforms=="WinXP"||Platforms=="WinServer2008")). The matrix will be setup and the unconfigured nodes are gray out, however, it is clear that it makes no sense for the node "WinXP" to exist on label Mac10.6 and etc. Although it is shown as diabled/unconfigured/gray, I would prefer you can provide a choice to remove them from the UI. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13005) Default recipients no longer save on configure system page
allenservedio created JENKINS-13005: --- Summary: Default recipients no longer save on configure system page Key: JENKINS-13005 URL: https://issues.jenkins-ci.org/browse/JENKINS-13005 Project: Jenkins Issue Type: Bug Components: email-ext Affects Versions: current Environment: Ubuntu Reporter: allenservedio In the "Extended E-mail Notification" section of the "Configure System" page, "Default Recipients" does not save any values any more. I have tried listing the email addresses with spaces as well as commas as delimiters. After adding them and saving the config, when I go back, the list is empty again. This is further confirmed by my not receiving the email when it is sent. Nothing appears in the jenkins log file when I save the recipients so I haven't a clue why this is happening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13004) Remove the nonsense configurations in multi-configuration project
[ https://issues.jenkins-ci.org/browse/JENKINS-13004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rsandell updated JENKINS-13004: --- Component/s: core (was: multi-slave-config) Moving the issue to core since it has nothing to do with the multi-slave-config plugin. > Remove the nonsense configurations in multi-configuration project > - > > Key: JENKINS-13004 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13004 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Windows, Mac >Reporter: Michael Lin >Assignee: rsandell > Labels: multi-configuration > > I use Jenkins to configure my multi-configuration project. > The Axes I use are: > Labels: Mac10.6, Mac10.7, and Windows > Platforms: Mac10.6, Mac10.7, WinXP, Win7, and WinServer2008 > Tasks: _App_Installer_, _App_Uninstaller_, and so on > A matrix will be generated, and I intend to let the tasks from windows > platforms go to execute on Windows machines(with Label "Windows"), by using a > filter as > (label=="Windows"&&(Platforms=="Win7"||Platforms=="WinXP"||Platforms=="WinServer2008")). > The matrix will be setup and the unconfigured nodes are gray out, however, it > is clear that it makes no sense for the node "WinXP" to exist on label > Mac10.6 and etc. Although it is shown as diabled/unconfigured/gray, I would > prefer you can provide a choice to remove them from the UI. > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1684) 403 errors on project configuration with matrix-based security
[ https://issues.jenkins-ci.org/browse/JENKINS-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Löber updated JENKINS-1684: Attachment: screenshot-1.jpg > 403 errors on project configuration with matrix-based security > -- > > Key: JENKINS-1684 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1684 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: shamoh >Priority: Critical > Attachments: 0-hudson-developer-permissions.png, > 1-hudson-developer-new_job.png, 2-hudson-developer-job_edit.png, > screenshot-1.jpg > > > Kirk True wrote to mailing list: > -- > Hi all, > We're running 1.198 and are trying to switch over to matrix-based security, > but > we're seeing some issues. > I have defined a user that has all permissions (job create, configure, etc.) > *except* Administer (under the "Overall" section). > When that user views an existing job configuration screen, we see the > following > error under the "Repository URL" and "Repository browser" URL sections: > Status Code: 403 > Exception: > Stacktrace: > (none) > Attempting to save the configuration as this user doesn't work either as we > get > the same 403 error on a screen all by itself. However, nothing seems to show > up > in the logs. > When that user attempts to create a new job, we get a new job configuration > screen (which has the same ‘403’ error right under the new job name), but this > time I see some output in the logs: > [webapp 2008/05/05 22:31:09] - Error while serving > http://hudson.qa.linkedin.com:8080null > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor748.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:103) > at org.kohsuke.stapler.Function.bindAndinvoke(Function.java:57) > at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:69) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:30) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:365) > at org.kohsuke.stapler.MetaClass$9.doDispatch(MetaClass.java:248) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:30) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:365) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:301) > at org.kohsuke.stapler.Stapler.service(Stapler.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) > at > winstone.ServletConfiguration.execute(ServletConfiguration.java:249) > at winstone.RequestDispatcher.forward(RequestDispatcher.java:335) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:52) > at > hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:28) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:44) > at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:85) > at winstone.FilterConfiguration.execute(FilterConf
[JIRA] (JENKINS-1684) 403 errors on project configuration with matrix-based security
[ https://issues.jenkins-ci.org/browse/JENKINS-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Löber reopened JENKINS-1684: - Currently exactly the same happens to us again. > 403 errors on project configuration with matrix-based security > -- > > Key: JENKINS-1684 > URL: https://issues.jenkins-ci.org/browse/JENKINS-1684 > Project: Jenkins > Issue Type: Bug > Components: security >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: shamoh >Priority: Critical > Attachments: 0-hudson-developer-permissions.png, > 1-hudson-developer-new_job.png, 2-hudson-developer-job_edit.png, > screenshot-1.jpg > > > Kirk True wrote to mailing list: > -- > Hi all, > We're running 1.198 and are trying to switch over to matrix-based security, > but > we're seeing some issues. > I have defined a user that has all permissions (job create, configure, etc.) > *except* Administer (under the "Overall" section). > When that user views an existing job configuration screen, we see the > following > error under the "Repository URL" and "Repository browser" URL sections: > Status Code: 403 > Exception: > Stacktrace: > (none) > Attempting to save the configuration as this user doesn't work either as we > get > the same 403 error on a screen all by itself. However, nothing seems to show > up > in the logs. > When that user attempts to create a new job, we get a new job configuration > screen (which has the same ‘403’ error right under the new job name), but this > time I see some output in the logs: > [webapp 2008/05/05 22:31:09] - Error while serving > http://hudson.qa.linkedin.com:8080null > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor748.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:103) > at org.kohsuke.stapler.Function.bindAndinvoke(Function.java:57) > at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:69) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:30) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:365) > at org.kohsuke.stapler.MetaClass$9.doDispatch(MetaClass.java:248) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:30) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:365) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:301) > at org.kohsuke.stapler.Stapler.service(Stapler.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) > at > winstone.ServletConfiguration.execute(ServletConfiguration.java:249) > at winstone.RequestDispatcher.forward(RequestDispatcher.java:335) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:52) > at > hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:28) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55) > at > hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:44) > at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:85) > at winstone.FilterCo
[JIRA] (JENKINS-13002) FileNotFoundException when trying to install version 1.22 of analysis collector plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13002: -- Assignee: (was: Ulli Hafner) Component/s: (was: analysis-collector) (was: core) > FileNotFoundException when trying to install version 1.22 of analysis > collector plugin > -- > > Key: JENKINS-13002 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13002 > Project: Jenkins > Issue Type: Bug > Components: update-center >Affects Versions: current > Environment: Linux - OpenSUSE 11.3, I am using 1.424.3 LTS Jenkins, > upgrading from 1.20 to 1.22 for analysis-collector >Reporter: keperry > > I receive the following error when trying to download the latest > analysis-collector plugin: > java.io.FileNotFoundException: > http://mirrors.jenkins-ci.org/plugins/analysis-collector/1.22/analysis-collector.hpi > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at > sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1458) > at java.security.AccessController.doPrivileged(Native Method) > at > sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1452) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1106) > at > hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:621) > at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:952) > at > hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1060) > at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:935) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > Caused by: java.io.FileNotFoundException: > http://mirrors.jenkins-ci.org/plugins/analysis-collector/1.22/analysis-collector.hpi > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1401) > at > sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2214) > at java.net.URLConnection.getHeaderFieldInt(URLConnection.java:596) > at java.net.URLConnection.getContentLength(URLConnection.java:491) > at > hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:620) > ... 9 more > Note: I tried switching from the stable update url to the normal, with no > avail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
