Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 26 07:17

    dependabot[bot] on maven

    (compare)

  • Oct 26 07:17

    dependabot[bot] on master

    Bump jenkins from 1.57 to 1.60 … (compare)

  • Oct 26 07:17
    dependabot[bot] closed #210
  • Oct 26 07:17

    dependabot[bot] on maven

    (compare)

  • Oct 26 07:17

    dependabot[bot] on master

    Bump mockito-core from 3.5.13 t… (compare)

  • Oct 26 07:17
    dependabot[bot] closed #211
  • Oct 26 07:17

    dependabot[bot] on maven

    (compare)

  • Oct 26 07:17

    dependabot[bot] on master

    Bump assertj-core from 3.17.2 t… (compare)

  • Oct 26 07:17
    dependabot[bot] closed #212
  • Oct 26 05:15
    dependabot[bot] labeled #212
  • Oct 26 05:15
    dependabot[bot] opened #212
  • Oct 26 05:15
    dependabot[bot] labeled #211
  • Oct 26 05:15
    dependabot[bot] opened #211
  • Oct 26 05:15

    dependabot[bot] on maven

    Bump assertj-core from 3.17.2 t… (compare)

  • Oct 26 05:15

    dependabot[bot] on maven

    Bump mockito-core from 3.5.13 t… (compare)

  • Oct 26 05:15

    dependabot[bot] on maven

    (compare)

  • Oct 26 05:15
    dependabot[bot] closed #206
  • Oct 26 05:15
    dependabot[bot] commented #206
  • Oct 26 05:15
    dependabot[bot] labeled #210
  • Oct 26 05:15
    dependabot[bot] opened #210
to make it work
but shouldn't matter anymore anyway
as you're about to do a real release?
(tag format will need to be updated)
Natasha Stopa
@stopalopa
it seems like things have been kind of messed up with the releases so I just wanted to make sure I got it right for the first real one
Tim Jacomb
@timja

process should be:

git checkout master
git pull
mvn release:prepare release:perform

after success
go to https://github.com/jenkinsci/plugin-installation-manager-tool/releases
edit the last draft

update the tag to the version you just released (release drafter will try help you here but it won't always have the right version say if you updated the major or minor version)
Edit the release notes to add any extra info then click "Publish release"

Natasha Stopa
@stopalopa
@kwhetstone sorry, I think I lost you again
so I tried to exit then rejoin
Kristin Whetstone
@kwhetstone
ok!
Still can't hear you :(
Natasha Stopa
@stopalopa
Sorry I don’t know what’s going on. It seems like I still have internet but neither Gitter or google hangouts are working for me
I started a Zoom meeting https://psu.zoom.us/j/480589458
maybe that will help
Joseph Petersen
@jetersen
:pray:
btw it would be awesome if you deleted this unwanted tag: https://github.com/jenkinsci/plugin-installation-manager-tool/releases/tag/90fa0de :sweat:
Natasha Stopa
@stopalopa
@kwhetstone you still there?
Kristin Whetstone
@kwhetstone
Yeah,
I'm the only one on the call though.
Natasha Stopa
@stopalopa
:/
oh
It says I’m also the only one on the call. Are you on the Zoom meeting?
Kristin Whetstone
@kwhetstone
whoops, just joined
Joseph Petersen
@jetersen
Natasha Stopa
@stopalopa
the struggle is so real
Natasha Stopa
@stopalopa
For using the bom to figure out upper bounds, is that something that would be done automatically with maven incorporation?
Natasha Stopa
@stopalopa
Also, since it will be hard to change them after the first real release, how do you guys feel about the cli option names? Some of them are kind of long…or do you think they’re ok?
Joseph Petersen
@jetersen
@stopalopa oh ya -h and --help is missing :D
Natasha Stopa
@stopalopa
ok, I can add those
Joseph Petersen
@jetersen
but other than that. Most of the time I suspect scripts will be running the commands so option length doesn't really matter
Natasha Stopa
@stopalopa
@casz RE: PR 61 Honestly I had also been thinking about adding another CLI option where users could specify that they wanted the latest of all plugins and their dependencies. I think right now they can specify that they want the latest version of a particular plugin but the version of the dependencies that are downloaded are dependent on whatever is in the update center metadata, which might not be the latest. Thoughts?
Joseph Petersen
@jetersen
both for yaml and plugin.txt it should be very easy to assume latest if version or second position in split is not provided :)
you could also add --update-version-to-latest which will find the newest version and put it into the file for you
Natasha Stopa
@stopalopa
I guess my question is, how important is it that if you specify that you want the latest version of a particular plugin, that the dependenices of that plugin are also the latest version?
Joseph Petersen
@jetersen
Even for dependencies, I would also say the latest is :+1: that's mostly how plugins.sh worked.
but that's my opinion :sweat:
I'd prefer to deal with the problem upfront instead of months or years down the line.
Natasha Stopa
@stopalopa
I think that was also one of the issues with install-plugins.sh - people wanted a little bit more control of the plugin versions that got installled.
Joseph Petersen
@jetersen
But it shouldn't be too hard to add the option to download latest dependencies as well :)
Kristin Whetstone
@kwhetstone
Right, the whole point is people wanted more control so just downloading the latest version isn't very helpful
:+1: will look at the slides!
They look good; I like including a challenges slide since that's also part of the software development process
Joseph Petersen
@jetersen
okay excluding the jenkinsci/plugin-installation-manager-tool#61
the master branch of the tool gives me a working instance but somewhat sad that I have to specify that I want the latest of icon-shim or other such plugins.
Or latest of pubsub-light without specifying it :sweat:
Natasha Stopa
@stopalopa
Ok…so the way you would want it to work would be that if a user specifies “latest” for a plugin, it would download the latest version of that plugin and the latest version of all of its dependencies by default, and if the user doesn’t want the latest version of the dependencies, they should have to specify that?
Kristin Whetstone
@kwhetstone
I think so
Natasha Stopa
@stopalopa
Ok. And is that something that should be included in the first official version?
Kristin Whetstone
@kwhetstone
Paart of me leans towards downloading latest plugins is actually against part of core of the tool. Part of the point is that it pulls in the specified versions of plugins across the board. -useLatest could be a flag to signify that that you want to download the latest version of the dependencies of ones without a version.
This is a tough one; I'm trying to think of where the behavior would most factor in.
Tim Jacomb
@timja

I wouldn't want an old dependency pulled in...
Plugins tend to have very conservative dependency versions.

But I also specify all plugins in my file so I get the versions of what I want :)

Kristin Whetstone
@kwhetstone
Yeah, but an "old dependency" wouldn't get pulled in right? The tool has already calculated the newest possible dependency