[JIRA] [m2release-plugin] (JENKINS-27075) override default SCM tag from ${project.artifactid}-${project.version} to something else

2015-02-23 Thread herb...@quartel.net (JIRA)














































Herbert Quartel
 created  JENKINS-27075


override default SCM tag from ${project.artifactid}-${project.version} to something else















Issue Type:


Improvement



Assignee:


James Nord



Attachments:


M2ReleasePlugin.PNG



Components:


m2release-plugin



Created:


23/Feb/15 10:11 AM



Description:


Is there a way to define what the default SCM tags is? Currently it is ${project.artifactid}-${project.version}
In our project the convention is ${project.version}.
This mean we need to edit with every release.

(see attachment)

Is there a way to change the default of ${project.artifactid}-${project.version} to ${project.version}?
Setting a properties file would be fine, but including it in Manage Jenkins would be great!




Environment:


Jenkins ver. 1.599

Maven Release Plug-in Plug-in 0.14.0




Project:


Jenkins



Priority:


Minor



Reporter:


Herbert Quartel

























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/d/optout.


[JIRA] [multijob-plugin] (JENKINS-27022) View the settings of 'Continuation condition to next phase when jobs' statuses are:', 'Abort all other job' and 'Kill the phase on' in the view of a MiltiJob

2015-02-19 Thread herb...@quartel.net (JIRA)














































Herbert Quartel
 created  JENKINS-27022


View the settings of Continuation condition to next phase  when jobs statuses are:,  Abort all other job and Kill the phase on in the view of a MiltiJob















Issue Type:


Improvement



Assignee:


Unassigned


Components:


multijob-plugin



Created:


19/Feb/15 9:22 AM



Description:


In order to verify if the MultiJob is configured properly it would be very helpfull if the overview of the Multijob would show:
on Phase level
Text or icon for the value of "Continuation condition to next phase  when jobs' statuses are:"
e.g.:
A: Always
S: SuccessFul
C: Completed
!F : Stable or not Stable, but not Failed
F: Failed

[on Job level:
Text or icon for the value of "Abort all other job"
e.g.:
Y: Yes
N: No

Text or icon for the value of "Kill the phase on"
e.g.:
F: Failure
N: Never
U: Unstable




Environment:


Jenkins ver. 1.599

MultiJob plugin ver.1.16




Project:


Jenkins



Priority:


Major



Reporter:


Herbert Quartel

























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/d/optout.


[JIRA] [multijob-plugin] (JENKINS-27022) View the settings of 'Continuation condition to next phase when jobs' statuses are:', 'Abort all other job' and 'Kill the phase on' in the view of a MiltiJob

2015-02-19 Thread herb...@quartel.net (JIRA)














































Herbert Quartel
 updated  JENKINS-27022


View the settings of Continuation condition to next phase  when jobs statuses are:,  Abort all other job and Kill the phase on in the view of a MiltiJob
















Change By:


Herbert Quartel
(19/Feb/15 9:23 AM)




Labels:


guimultijobpluginview



























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/d/optout.


[JIRA] [matrix-auth-plugin] (JENKINS-25567) Matrix-based security does not allow read-only on Configure System

2014-11-12 Thread herb...@quartel.net (JIRA)














































Herbert Quartel
 created  JENKINS-25567


Matrix-based security does not allow read-only on Configure System















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


matrix-auth-plugin



Created:


12/Nov/14 2:17 PM



Description:


Hi, I do not exactly know it this is a bug or not.

For our jenkins setup we use Matrix-based security using 2 groups (CI_Admins and CI_Users)

We want to prevent that CI_Users ALTER Jenkins configuration (So the stuff under Manage Jenkins) , however , they should be able to VIEW the Jenkins configuration, and most notably the Global properties under Configure System.

I do not see a way to do this using the security matrix.
Overall-- Read is enabled for CI_Users





Environment:


Jenkins ver. 1.585, 	

Matrix Authorization Strategy Plugin 1.1	




Project:


Jenkins



Labels:


configuration
jenkins
authorisation




Priority:


Minor



Reporter:


Herbert Quartel

























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/d/optout.


[JIRA] [label-linked-jobs] (JENKINS-25188) Orphaned jobs do not show jobs without label when all nodes set to Labe restrictions

2014-10-17 Thread herb...@quartel.net (JIRA)














































Herbert Quartel
 created  JENKINS-25188


Orphaned jobs do not show jobs without label when all nodes set to Labe restrictions















Issue Type:


Bug



Assignee:


Dominique Brice



Components:


label-linked-jobs



Created:


17/Oct/14 7:36 AM



Description:


When all nodes in Jenkins are configured with Usage : Only run jobs with Label restrictions, then jobs without a label are not shown in the Labels Dashboard under orphaned jobs.

I think these jobs should be listed under orphanded jobs, since these jobs will remain waiting.




Environment:


Jenkins ver. 1.583 , label linked ver. 2.0.4




Project:


Jenkins



Labels:


plugin
job
gui
user-experience




Priority:


Major



Reporter:


Herbert Quartel

























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/d/optout.


[JIRA] [label-linked-jobs] (JENKINS-25188) Orphaned jobs do not show jobs without label when all nodes set to Label restrictions

2014-10-17 Thread herb...@quartel.net (JIRA)














































Herbert Quartel
 updated  JENKINS-25188


Orphaned jobs do not show jobs without label when all nodes set to Label restrictions
















Change By:


Herbert Quartel
(17/Oct/14 7:36 AM)




Summary:


Orphanedjobsdonotshowjobswithoutlabelwhenallnodessetto
Labe
Label
restrictions



























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/d/optout.


[JIRA] [label-linked-jobs] (JENKINS-25163) Add list of jobs that do not have a label

2014-10-15 Thread herb...@quartel.net (JIRA)














































Herbert Quartel
 created  JENKINS-25163


Add list of jobs that do not have a label















Issue Type:


Improvement



Assignee:


Dominique Brice



Components:


label-linked-jobs



Created:


15/Oct/14 7:44 AM



Description:


Add a section in the Label dashboard that shows all jobs without label.

I used NotePad++ - Find in Files (on Jenkins jobs) with regular _expression_:
/scm\W^(?!.assignedNode).$
which found the jobs that do not have the 'Restrict where this project can be run' checkbox set.

Can this functionality be added?




Environment:


Jenkins ver. 1.583, Label linked jobs 2.0.4




Project:


Jenkins



Labels:


plugin
user-experience
configuration
gui




Priority:


Minor



Reporter:


Herbert Quartel

























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/d/optout.