Forked to https://github.com/jenkinsci/build-timestamp-plugin

Still not entirely sure the use case is sufficiently different, but not 
convinced it's not either.

There's a corresponding component for the plugin on issues.jenkins-ci.org and 
you're the default assignee.

> On 18.12.2015, at 16:14, Hao Chen <[email protected]> wrote:
> 
> No, she'll not involved. 
> But Maven and Gradle related. 
> 
> I used to set timestamps in Maven and Gradle, to filter package build info 
> properties, to archive build packages with a timestamp (in Maven and Gradle 
> plugins). This requires a same timestamp with different formats. 
> 
> Until I stared to work with AWS, when you try to deploy package to Elastic 
> Beanstalk and put a copy to S3 bucket, you will find there's no way to name 
> the version in Elastic Beanstalk, and the archive in S3 bucket with a 
> timestamp, with Jenkins plugin. (BTW, there are two Elastic Beanstalk 
> plugins, and one of them is a fork of the other one)
> 
> And in Maven and Gralde, we can use those timestamp variables. One timestamp, 
> different formats, keeps the built artifacts and the job history info 
> consistent. 
> 
> —
> Hao
> 
> 
> On Fri, Dec 18, 2015 at 10:56 PM, Benjamin Lau <[email protected]> 
> wrote:
> 
> If you want the value in an environment variable I assume you're using it in 
> a bit of shell code (maybe a bad assumption). But if that's the case why not 
> just generate the other formats using the date command?
> 
> BUILD_TIMESTAMP_AWS=$(date -d "@$(date -d "$BUILD_TIME_STAMP" +%s)" 
> +%Y%m%d-%H%M%S)
> 
> or something of that nature. Not sure what value is in the existing 
> environment variable... and if it's a unix time... you can simplify things 
> like this:
> 
> BUILD_TIMESTAMP_AWS=$(date -d "@$BUILD_TIMESTAMP" +%Y%m%d-%H%M%S)
> 
> On Fri, Dec 18, 2015 at 6:35 AM, Hao Chen <[email protected]> wrote:
> I had explained the difference between ZenTimestamp and the one I'm creating. 
> 
> I cloned ZenTimestamp to my workspace and read the source code of it, then I 
> decided to create this plugin. 
> 
> I need to add more timestamp variables with different formats for different 
> use cases. 
> While ZenTimestamp allows you to export only one variable, but you can use 
> different formats in each node and each job. 
> Adding the feature to ZenTimestamp, makes it wired. 
> 
> It's from a different practice. 
> 
> —
> Hao
> 
> 
> On Fri, Dec 18, 2015 at 10:15 PM, Slide <[email protected]> wrote:
> 
> There is another plugin which provides a BUILD_TIMESTAMP environment variable 
> and allows some formatting. Zentimestamp or something like that. Could the 
> functionality you are adding be added to that existing plugin?
> 
> 
> On Fri, Dec 18, 2015, 07:09 Hao Chen <[email protected]> wrote:
> If I recall correctly, timestamper plugin is totally a different thing, it 
> adds timestamps to the build console of each line. While 
> secondary-timestamper is to set an extra timestamp as description in the 
> build history list. 
> 
> Each plugin has a different purpose. 
> 
> —
> Hao
> 
> 
> On Fri, Dec 18, 2015 at 9:53 PM, Baptiste Mathus <[email protected]> wrote:
> 
> Hi,
> 
> There are (at least) already 3 timestamping plugins:
> 
> * https://wiki.jenkins-ci.org/display/JENKINS/Timestamper
> * https://wiki.jenkins-ci.org/display/JENKINS/secondary-timestamper-plugin
> * https://wiki.jenkins-ci.org/display/JENKINS/ZenTimestamp+Plugin
> 
> The second one explicitly lists TZ as a goal.
> 
> Did/would you consider contributing your additional feature(s) to one of them?
> 
> Maybe it'd be beneficial to users to have a bit more unity in that field?
> 
> Cheers
> 
> 
> 2015-12-18 10:58 GMT+01:00 Hao CHEN <[email protected]>:
> I cloned the repo to local and read the source code before I decided to 
> create a different one. 
> ZenTimestamp exports only one variable to the build, but can be configured to 
> use different formats for each job and each node. 
> 
> While I need to
> 1. Time zone support, which is relatively  easy to add to zentimestamp
> 2. More timestamp variables and formats. A same timestamp with different 
> formats, can be used in different places, such as folder names or file names 
> using a path friendly format, JSP pages using a human friendly formats. And 
> these formats are set up only once in global config, they can be used in the 
> corp-width as a naming convention. 
> To do this is almost changing every thing in ZenTimestamp. 
> 
> Hao CHEN
> 
> 
> 
> 
> On Fri, Dec 18, 2015 at 1:17 AM -0800, "Daniel Beck" <[email protected]> wrote:
> 
> 
> On 16.12.2015, at 10:15, Hao Chen <[email protected]> wrote:
> 
> > I'd like to create a plugin to expose build timestamp to as env vars.
> 
> This looks really similar to ZenTimstamp plugin -- why are you not using 
> that? Timezone support could be added if that's missing.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/X5YdoL6IjdI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/F23577C3-4B37-43B0-916E-CC0BA61F453E%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/BAY407-EAS416052DF8A3F0AF609426ECC7E10%40phx.gbl.
> 
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> -- 
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/X5YdoL6IjdI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4QWGGMBAyxG_NAqUwcrtR4YGdZOaMKpZYUHy345Oce8Q%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1450447737190.a4a8a8d3%40Nodemailer.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/X5YdoL6IjdI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfo6E%2BeOZ9dkfTSRzsPL-ZLy4w5zVwM8zPqJPbw2HDd9w%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1450449306768.85bdd81a%40Nodemailer.
> 
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/X5YdoL6IjdI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BvtdQatzvng8jHGBY%2Bc9Ef_rZqTft8rRNdkvzo9x0Z1sKoQug%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1450451672493.e8d0866f%40Nodemailer.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/37843FFA-65F8-456C-8A31-D71A359A6E62%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to