Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Matt Sicker
    @jvz
    I merged some of the open PRs. I think we’re just about ready to release
    Matt Sicker
    @jvz
    Since there aren’t enough features remaining in this plugin to do another Outreachy round, any suggestions on a project for the next one?
    Matt Sicker
    @jvz
    @gayathrirajendar @aarthira let me know if there’s anything else you want to merge before we make a 1.0 release. I’d like to do that tomorrow if possible
    Aarthi Rajaraman
    @aarthira
    @jvz , I checked your comments. So, I think we can release 1.0 now and keep improving this further.
    Gayathri Rajendar
    @gayathrirajendar
    curious about what does a release mean. Do we use GitHub release and make a copy of the code at this point in time?
    a side effect of this is a github release is created, yes, but the main thing is the process of uploading the hpi file to plugins.jenkins.io or whatever the repository URL is
    that’s all automated by a maven plugin, though
    Matt Sicker
    @jvz
    a co-worker suggested an interesting project idea just now that might work well as the next outreachy project: https://issues.jenkins-ci.org/browse/JENKINS-57351
    @gayathrirajendar @aarthira would either of you like to do the honors of making our 1.0 plugin release? or should I release it?
    Matt Sicker
    @jvz
    let me know within the next, say, two hours, or I’ll go ahead and make the release
    Matt Sicker
    @jvz
    Ok, I’m going ahead with 1.0
    Matt Sicker
    @jvz
    I’ve pushed the tag for 1.0 along with publishing the plugin to repo.jenkins-ci.org in https://repo.jenkins-ci.org/releases/io/jenkins/plugins/audit-log/1.0/
    which should eventually show up at this URL: https://plugins.jenkins.io/audit-log
    Matt Sicker
    @jvz
    plugin page is up, though it doesn’t have much there yet. also, maintainers says “matt” which is just my local username lol
    Aarthi Rajaraman
    @aarthira
    Thanks a lot :)
    How do we add documentation for this as it is in the other plugins page?
    Matt Sicker
    @jvz
    Usually that’s generated from the Jenkins wiki page for the plugin, but we didn’t make one. I wonder if there’s any other content we can display on the plugin page or if we have to use a wiki page for that (not the GitHub wiki)
    Matt Sicker
    @jvz

    oh hey look at that: https://plugins.jenkins.io/audit-log

    new feature just rolled out on plugins.jenkins.io to use the readme if it’s there

    Oleg Nenashev
    @oleg-nenashev
    It uses GitHub only if the GitHub repo is set as <url> in pom.xml. But yeah, it is pretty much smooth for plugin developers
    Matt Sicker
    @jvz
    Yeah, we already had that URL set since we never made a wiki page
    Oleg Nenashev
    @oleg-nenashev
    There is pretty much no reason to create Wiki pages now, except setting up plugin labels
    There is a task for supporting labels from GitHub tho
    Matt Sicker
    @jvz
    Oh is that how you categorize plugins on the site? I was wondering
    Matt Sicker
    @jvz
    @/all good luck with the presentations today!
    Oleg Nenashev
    @oleg-nenashev
    @aarthira @gayathrirajendar Please join with 10 minutes advance so that we check hardware. Also, would be nice if you could join https://gitter.im/jenkinsci/gsoc-sig for Q&A
    Oleg Nenashev
    @oleg-nenashev
    @aarthira @gayathrirajendar https://zoom.us/j/730463146
    Aarthi Rajaraman
    @aarthira
    Thanks
    Tracy Miranda
    @tracymiranda
    nice presentation thanks @aarthira and also @jvz
    Aarthi Rajaraman
    @aarthira

    @gayathrirajendar Could not install Zoom and had some issues with it and I had to take up the presentation in the last minute on behalf of her.

    I became nervous. Didn't I?

    Matt Sicker
    @jvz
    you did great!
    Marky Jackson
    @markyjackson-taulia
    Agreed, you did awesome and super great work!
    Matt Sicker
    @jvz
    if I ever figure out that one property substitution bug that stalled us early on, I’ll make sure to let you know. I’ve been looking at refactoring the log4j plugin subsystem for 3.0, and I’ve noticed that the string substitution thing is fairly inconsistent
    Aarthi Rajaraman
    @aarthira
    Oh. For now we have the audit.log always within the logs folder.
    Matt Sicker
    @jvz
    it almost seems like you can’t use lookups inside <properties>, but I might be wrong
    Aarthi Rajaraman
    @aarthira

    Thanks @jvz , @markyjackson-taulia , @tracymiranda

    @tracymiranda , May I answer your questions here after the call? I did not hear them well in the call.

    Tracy Miranda
    @tracymiranda
    yes, please do - happy to hear any ways we can improve things & understand what the challenges are with a project like this
    Oleg Nenashev
    @oleg-nenashev
    Thanks for the presentation @aarthira !
    Matt Sicker
    @jvz
    this might be relevant if we start getting fancier with the audit log html output: https://issues.jenkins-ci.org/browse/JENKINS-41891
    particularly if we include any css or js files
    Oleg Nenashev
    @oleg-nenashev
    It would be great to have a dedicated Outreachy page under https://jenkins.io/events/ or under Advocacy&Outreach SIG
    Matt Sicker
    @jvz
    jenkins-infra/jenkins.io#2484 for a new blog post related to this. @aarthira and @gayathrirajendar please take a look when you have some time
    Matt Sicker
    @jvz
    @davidolorundare we removed the default assignee on jira since we use github issues now (where we don’t have a default assignee which is ok)
    Aarthi Rajaraman
    @aarthira
    @jvz Thank you so much for the blog content. It was a great experience. After a short wrapping break, will continue to contribute :)
    Matt Sicker
    @jvz
    sounds great!
    Marky Jackson
    @markyjackson-taulia
    This blog post makes me so sad
    Sladyn
    @sladyn98
    @markyjackson-taulia I think should have this in the advocacy and outreach sig

    This blog post makes me so sad

    Agreed