[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
Alexander Artemov commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing It works for me as well. Thank you for the fix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Alexander Artemov edited a comment on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Still reproduceble This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Now I have correct date 2 weeks in the future, but anyway I have to login 10 times a day because I often become logged out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-17524) NPE when renaming job in My Views
Alexander Artemov edited a comment on JENKINS-17524 NPE when renaming job in My Views It isn't connected with the view. At least I have the same error when renaming any job. In fact the job is renamed despite of this error. Anyway this error annoys me very much. This error is on 1.510. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-17524) NPE when renaming job in My Views
Alexander Artemov commented on JENKINS-17524 NPE when renaming job in My Views It isn't connected with the view. At least I have the same error when renaming any job. In fact the job is renamed despite of this error. Anyway this error annoys me very much. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-17524) NPE when renaming job in My Views
Alexander Artemov edited a comment on JENKINS-17524 NPE when renaming job in My Views It isn't connected with the view. At least I have the same error when renaming any job. In fact the job is renamed despite of this error. Anyway this error annoys me very much. I have this error on 1.510 version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov reopened JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session I still have the same issue in Jenkins 1.502 - every half an hour - hour I am logged off and have to login again. Change By: Alexander Artemov (20/Feb/13 11:30 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session It looks like: YWFydGVtb3Y6MTM2MTQyNzY0NDA0OTpjZjdlYjZmNTI2NjA2ZDg1Mzc5NWEwMDkyMGUzODhmMw== It's expiration date it 6.5 hours earlier than the present time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session No, jenkins runs at the same time as my machine. Jenkins runs on the server which time is the same as on my machine. It's Feb 20, 2013 5:49:00 PM now in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Created and the date is ok - Feb 21, 2013 10:54:37 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov edited a comment on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Created and the date is ok - Feb 21, 2013 10:54:37 (this is our local time - Russia, Saint-Petersburg) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15926) Build Failure Analyzer with Timestamper output ugly.
Alexander Artemov reopened JENKINS-15926 Build Failure Analyzer with Timestamper output ugly. I have 1.3.0 version, but the problem is still actual. I can see in my log something like: [8mha:dB+LCABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtpm64sNhAAbQyiWB [0mStarted by user [8mha:mh+LCABb85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzBEgY+/dLi1CL9xMSiktTc/DIAGVLEucM= Change By: Alexander Artemov (04/Feb/13 3:04 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Alexander Artemov reopened JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option The same with me in 1.499 - the issue was not solved. Failing to obtain server/slave-agent .jnlp java.io.IOException: Failed to load server/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:230) at hudson.remoting.Launcher.run(Launcher.java:192) at hudson.remoting.Launcher.main(Launcher.java:168) Change By: Alexander Artemov (15/Jan/13 6:54 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. 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
[
https://issues.jenkins-ci.org/browse/JENKINS-12998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160665#comment-160665
]
Alexander Artemov commented on JENKINS-12998:
-
I suggest you to use the following plugin, before this issue will be resolved:
https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin
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
