[JIRA] [core] (JENKINS-16781) Job and Project naming convention
Title: Message Title
Sagayaraj David commented on JENKINS-16781
Re: Job and Project naming convention
Hi Joris,
I am unable to include conditional regex (if) in the pattern (_)?(?(1)[\w] {1,15}
). Meaning _ is a optional string, if found then a string of length 1 to 15 should be available. Could you please check and let me know
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-16781) Job and Project naming convention
Joris van der Pol commented on JENKINS-16781 Job and Project naming convention @Daniel Beck: ok, that explains the job/project convention. With that in mind, I don't see a problem. I'll close this issue. 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] [core] (JENKINS-16781) Job and Project naming convention
Joris van der Pol closed JENKINS-16781 as Not A Defect Job and Project naming convention Change By: Joris van der Pol (24/Nov/13 10:24 PM) Status: Open Closed Resolution: NotADefect 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] [core] (JENKINS-16781) Job and Project naming convention
Joris van der Pol updated JENKINS-16781 Job and Project naming convention Change By: Joris van der Pol (19/Nov/13 9:33 PM) Attachment: delete_project.png Attachment: new_job.png 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] [core] (JENKINS-16781) Job and Project naming convention
Joris van der Pol commented on JENKINS-16781 Job and Project naming convention Jenkins allows Jobs (e.g. Monitor Job)and Projects (e.g. Free-Style Software Project) to be created. But this convention is not always followed. Create a new Job and Delete a Project for example. It is to me unclear what the difference is between a Job and a Project. 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] [core] (JENKINS-16781) Job and Project naming convention
Daniel Beck commented on JENKINS-16781 Job and Project naming convention Joris: Projects are a subtype of Job (specifically, the kind that can be scheduled and disabled). That's why you select 'Create Job' (all types of job), but 'Delete Project' (it's known that the specific item is a project). Or are there some places where it says 'Project' while referring to all job types, or 'Job' when it's known it's about a specific subtype? 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] [core] (JENKINS-16781) Job and Project naming convention
Daniel Beck edited a comment on JENKINS-16781 Job and Project naming convention Joris: Projects are a subtype of Job (specifically, the kind that can be scheduled and disabled). That's why you select 'Create Job' (all types of job), but 'Delete Project' (it's known that the specific item is a project). If you have a 'Monitor external job', it says 'Delete Job'. Or are there some places where it says 'Project' while referring to all job types, or 'Job' when it's known it's about a specific subtype? 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] [core] (JENKINS-16781) Job and Project naming convention
martin naughton commented on JENKINS-16781 Job and Project naming convention even in the programming of jenkins is modeled in that way. You have a Job object which you can cast to a project object depending on if it is a project object. 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] [core] (JENKINS-16781) Job and Project naming convention
martin naughton commented on JENKINS-16781 Job and Project naming convention what do you mean you can not delete a job? project and job are the same in regards to the user to my knowledge. some times can not tell the difference. 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.
