Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: plugin-proposals
-
Labels:
-
Similar Issues:
Description
The following stackoverflow question asks for how to get the creation date of a job within Jenkins.
http://stackoverflow.com/questions/25724894/how-to-get-the-jenkins-created-data-and-time
I haven't been able to figure out a way to capture the creation date of a Job from jenkins core. I did find that using the jobConfigHistory plugin provides detail on the create operation of a Job which would be possible to scrape, but I would prefer the core expose this information. For some reason, jobConfigHistory usually shows two change operations before the create operation...which is also a little strange.
Please let me know if I've overlooked an easy way to get the date of creation of a Job. Otherwise, maybe someone knows how to extend jenkins to provide this detail in the project_config of the jenkins api? Or even a way to easily get the create date from the jobConfighistory plugin using groovy script? I'm still researching myself.
Thanks.
--dave
http://dave.thehorners.com/tech-talk/programming/226-testing-release-engineering-ci-building-code-that-deploys-and-runs-like-it-should
Attachments
Activity
Daniel Beck, the requirement documented by this JIRA is that Jenkins core provides the creation date of a job. Can this be added and if this ticket (it is labeled as component plugin-proposals) is not correct, could you modify/assign it to the proper bucket? The job creation time would be a very useful feature.
Mario Jauvin
added a comment - Daniel Beck , the requirement documented by this JIRA is that Jenkins core provides the creation date of a job. Can this be added and if this ticket (it is labeled as component plugin-proposals) is not correct, could you modify/assign it to the proper bucket? The job creation time would be a very useful feature. I'd be happy to reassign the issue to core. And then, as core maintainer, reject it as Won't Do 
@db how useful would it be to do that. People are telling this would be a useful feature and you turn around and simply state “won’t do”. Not what I expected.
Mario Jauvin
added a comment - @db how useful would it be to do that. People are telling this would be a useful feature and you turn around and simply state “won’t do”. Not what I expected. I'm not going to work on this, I doubt anyone on the core team will, and I will expect that outside contributions to core aren't half-baked either. In other issues' discussions I've been told that rejecting issues is preferable to just never doing anything and letting issues linger for a decade. I'm fine either way.
Agreed that this should be a core property of a job. Can this be placed into the <properties> block of a job's config.xml?