15:04:20 <edwarnicke> #startmeeting
15:04:20 <odl_meetbot> Meeting started Mon Jan 27 15:04:20 2014 UTC.  The chair is edwarnicke. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:04:20 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:04:28 <edwarnicke> #topic rollcall
15:04:33 <edwarnicke> Who's here and from which projects?
15:04:44 <goldavberg> #info goldavberg for lispflowmapping
15:04:46 <hideyuki> #info Hideyuki Tai for VTN Project
15:05:22 <tykeal> #info Andrew Grimberg infrastructure support
15:05:22 <edwarnicke> #info Ed Warnicke controller
15:05:30 <Kudo> #info Kudo from VTN
15:05:45 <oflibMichal> #info oflibMichal for the openflowjava
15:05:45 <dmm> there are folks hanging out over on the webex
15:06:26 <goldavberg> what webex?
15:06:50 <tykeal> that's a good question. What webex
15:07:03 <gera> thought webex is only if we need to share screens
15:07:05 <edwarnicke> Guys
15:07:11 <colindixon> #info colindixon here for generally getting things done
15:07:12 <edwarnicke> Webex is a total distraction unless needed
15:07:16 <dmm> Hydrogen Release Artifact Cutting Party
15:07:22 <edwarnicke> Lets do this on IRC unless we *need* voice and screenshare
15:07:31 <colindixon> edwarnicke: +1
15:07:40 <dmm> looks like Phil scheduled this
15:07:47 <oflibMichal> edwarnicke: +1
15:07:51 <dmm> I'll tell folks to come over here if they want
15:07:56 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller...
15:08:11 <rovarga> #info Robert Varga bgpcep
15:08:57 <edwarnicke> rovarga, can you also represent yangtools ?
15:09:24 <abhijitkumbhare> #info Abhijit Kumbhare ofplugin
15:09:30 <rovarga> edwarnicke: let me syncup with Tony
15:09:34 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller, bgpcep, openflowplugin
15:09:42 <Madhu> #info Madhu for ovsdb (on & off - this is a bad time for me)
15:09:56 <prasanna> #info Prasanna for OF Plugin
15:10:01 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller, bgpcep, openflowplugin, ovsdb (somewhat)
15:10:06 <Christine_> #info Christine for SNMP4SDN
15:10:07 <edwarnicke> Madhu: can you get Brent in to cover?
15:10:19 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller, bgpcep, openflowplugin, ovsdb (somewhat), snmp4sdn
15:10:34 <colindixon> edwarnicke: networkstatic is around
15:10:35 <Madhu> trying.
15:10:42 <Konstantin_> #info Konsta and Gera for defense4all
15:10:48 <networkstatic> rogr here
15:10:57 <michal_rehak> #info michal_rehak / openflowplugin
15:10:58 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller, bgpcep, openflowplugin, ovsdb, snmp4sdn, defense4all
15:11:31 <colindixon> I'll try to scare up asheikh or regXboi
15:12:26 <edwarnicke> I think we are missing affinity, opendove, and integration
15:12:38 <rovarga> #info Robert Varga for yangtools
15:13:12 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller, bgpcep, openflowplugin, ovsdb, snmp4sdn, defense4all, yangtools
15:13:21 <colindixon> edwarnicke: regXboi is incoming
15:14:19 <regXboi> ok, made it
15:14:25 <regXboi> #info regXboi for opendove
15:14:26 <colindixon> regXboi: you can #info in
15:14:31 <colindixon> too late :p
15:14:51 <regXboi> done enough of these now to have a clue about some of the ropes
15:15:03 <chrisprice_> Luis is not in the office as of yet.  I'll make sure he's wrangled when he arrives.
15:15:48 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller, bgpcep, openflowplugin, ovsdb, snmp4sdn, defense4all, yangtools, opendove
15:16:28 <suchiraman> #info suchiraman here
15:16:36 <edwarnicke> suchiraman: for affinity?
15:16:43 <suchiraman> #info suchiraman for affinity
15:16:52 <edwarnicke> So I see folks from lispflowmapping, vtn, openflowjava, controller, bgpcep, openflowplugin, ovsdb, snmp4sdn, defense4all, yangtools, opendove, affinity
15:17:05 <edwarnicke> I believe we are only missing integration
15:17:42 <paiwei> #info paiwei for snmp4sd
15:17:55 <cdub> #info Chris Wright here
15:18:11 <phrobb> #info Phil Robb is here
15:18:18 <dmm> #info dmm here
15:18:43 <dkutenic1> #info dkutenic for bgpcep
15:18:59 <edwarnicke> chrisprice_: Any word on Luis ?
15:19:53 <chrisprice_> edwarnicke: not yet, will get an eta
15:19:55 <edwarnicke> cdub: Could you change the topic on #opendaylight pointing here in case there is confusion
15:20:17 <edwarnicke> OK... shall we start cutting yangtools then?
15:20:22 <edwarnicke> Which is first up
15:20:27 <cdub> edwarnicke: yeah, i did just a few minutes ago
15:20:40 <edwarnicke> cdub: Thanks :)
15:20:48 <edwarnicke> rovarga: Are you ready to cut yangtools ?
15:21:44 <rovarga> I think so :)
15:22:15 <edwarnicke> Could you run your prepare job one last time to make sure all is well
15:22:20 <Madhu> edwarnicke: change topic please
15:22:25 <edwarnicke> And then we can run your release job
15:22:27 <edwarnicke> Sounds good?
15:22:34 <edwarnicke> #topic cutting yangtools
15:22:41 <edwarnicke> Madhu: Thanks for the prompt :)
15:22:48 <rovarga> https://jenkins.opendaylight.org/yangtools/job/yangtools-bulk-release-prepare-only/13/
15:22:59 <rovarga> #link https://jenkins.opendaylight.org/yangtools/job/yangtools-bulk-release-prepare-only/13/
15:24:41 <rovarga> ETA 9 minutes
15:27:19 <hideyuki> Is someone from Integration group here?
15:27:38 <colindixon> hideyuki: we're still waiting for Luis, chrisprice_ was hunting him
15:27:47 <hideyuki> colindixon: thank you.
15:28:59 <edwarnicke> Looks like yangtools prepare only has about 4 minutes or so left
15:29:28 <Madhu> just to make sure.
15:29:38 <Madhu> prepare-only is the dry-run that we were running so far. correct ?
15:29:59 <edwarnicke> Madhu: Yes, dry-run
15:30:02 <edwarnicke> Make sure it all works
15:30:04 <edwarnicke> Then do it
15:30:12 * edwarnicke paranoid
15:30:21 <Madhu> +1
15:30:22 * regXboi joins edwarnicke in that space
15:30:36 <Madhu> with so many changes over the weekend :) we need that paranoia
15:30:56 <goldavberg> can't we all run the prepare only simultaneously?
15:31:09 <goldavberg> if its only a dry run
15:31:16 <Madhu> goldavberg: good idea
15:31:51 <tykeal> changes over the weekend? you don't say.
15:31:52 <edwarnicke> goldavberg: Sort of
15:32:00 <edwarnicke> Let me explain my thoughts on this
15:32:00 <rovarga> well, we'll need to re-run it as we get rid of SNAPSHOT dependencies
15:32:05 * tykeal glares at the jenkins / nexus systems having issues over the weekend
15:32:09 <edwarnicke> And yangtools is a little special because its going first
15:32:22 <edwarnicke> But for things that depend on things
15:32:31 <edwarnicke> I think it should be
15:32:42 <Madhu> tykeal: sorry for disturbing u yesterday during ur church visit :)
15:32:47 <edwarnicke> run your change-versions job (to update to the newly released versions) and merge that patch
15:33:11 <edwarnicke> run your dry run job (turning false the IGNORE_SNAPSHOTS flag... because you should no longer have snapshots)
15:33:17 <edwarnicke> run your release job
15:33:20 <tykeal> oh, that's ok Madhu, edwarnicke snagged me Saturday evening while I was coming back from my nephew's b-day party ;)
15:33:22 <edwarnicke> Something roughly like that
15:33:42 <edwarnicke> That said, goldavberg it probably is a good idea for everyone to run their dryrun with IGNORE_SNAPSHOTS true while we are waiting for yangtools
15:33:47 <edwarnicke> Just to make sure that part is good
15:34:01 <regXboi> um
15:34:04 <regXboi> release job?
15:34:22 <edwarnicke> regXboi: We can fix this :)
15:34:32 <regXboi> point me at a job to copy and I'll go copy in the background
15:34:36 <edwarnicke> regXboi: do you have a dryrun job ?
15:34:39 <rovarga> alright, done. now what? :)
15:34:49 <edwarnicke> Five steps:
15:34:53 <regXboi> edwarnicke - move the main stream along
15:34:59 <edwarnicke> 1)  Copy your dryrun job to a release job
15:35:09 <edwarnicke> 2) Remove the IGNORE_SNAPSHOT stuff
15:35:18 <edwarnicke> (both as a parameter and in the maven goals)
15:35:36 <edwarnicke> 3)  Add to the maven goals release:perform
15:35:46 <edwarnicke> 4) Change Source Code Management -> Git -> Branches to build -> Advanced -> Checkout/merge to local branch (optional) to $BRANCH
15:35:53 <edwarnicke> 5) remove the pre-build step
15:36:00 <edwarnicke> I'm happy to look over it when you've done that
15:36:44 <goldavberg> what about the release job?
15:37:01 <regXboi> um...
15:37:02 <edwarnicke> goldavberg: Do you have conversations about the last little bit of commentary
15:37:14 <rovarga> edwarnicke: want to go over https://jenkins.opendaylight.org/yangtools/job/yangtools-bulk-release/ or should I just run it now?
15:37:21 <regXboi> #4 doesn't work for me - I'm on a different release of jenkins
15:37:25 <edwarnicke> rovarga: Let me take a quick look
15:37:39 <edwarnicke> tykeal: Help
15:38:01 <tykeal> regXboi: which project?
15:38:04 <regXboi> but I think I have what you want
15:38:06 <goldavberg> edwarnicke: isn't the result of what you said the release job which we have already?
15:38:10 <regXboi> tykeal: opendove
15:38:21 * tykeal can't keep everyone's projects straight in his head anymore
15:38:22 <regXboi> opendove-bulk-release job I just created
15:38:33 <edwarnicke> goldavberg: If you have one, probably
15:38:40 <regXboi> tykeal: no worries - I figured that - that's why I didn't give you grief
15:38:41 <edwarnicke> regXboi didn't have one
15:38:50 * regXboi missed the memo
15:38:54 <goldavberg> edwarnicke: i copied the controllers release job
15:39:25 <Madhu> yes
15:39:27 <edwarnicke> rovarga: Looks good... proceed
15:39:27 <Madhu> that is prefered
15:39:37 <Madhu> i copied the controller release job as well
15:39:41 <tykeal> regXboi: looks like you found the correct setting
15:39:52 <regXboi> tykeal: thanks
15:40:03 <edwarnicke> #link https://jenkins.opendaylight.org/controller/job/controller-bulk-release-2/ is the job controller will be using
15:40:03 <rovarga> #link https://jenkins.opendaylight.org/yangtools/job/yangtools-bulk-release/1/
15:40:23 <tykeal> though I think the branch name is probably supposed to be just $BRANCH per edwarnicke's instructions not $BRANCH-doingrelease-$JOB_NAME-$BUILD_NUMBER
15:40:23 <colindixon> is everyone running their dry run at once right now going to kill our build servers for other tasks
15:41:38 <tykeal> colindixon: shouldn't kill them, might make things a little slow though
15:41:58 <goldavberg> #link https://jenkins.opendaylight.org/lispflowmapping/job/lispflowmapping-bulk-release/
15:42:09 <tykeal> I moved nexus out of a VM last night and onto hardware so hopefully we avoid any 504 issues that we've been seeing off and on
15:44:36 <regXboi> so it looks like I've got a problem with the opendove version check job that evidently cropped up in the last week... looking at consoles now
15:46:52 <regXboi> hmm... that's odd
15:47:21 <edwarnicke> regXboi: I though the version checks were running daily?
15:47:53 <regXboi> doesn't look like it here - these have been running weekly
15:48:08 * regXboi suspects he messed up the scheduling
15:49:36 <edwarnicke> regXboi: Fix the problem not the blame.
15:49:49 <Christine_> just done for snmp4sdn as edwarnick's steps
15:49:53 <Christine_> #link https://jenkins.opendaylight.org/snmp4sdn/job/snmp4sdn-bulk-release/
15:50:16 <Christine_> should I build it now
15:50:46 <edwarnicke> Do not run your release yet
15:51:01 <edwarnicke> (that was meant for Christine_
15:51:02 <edwarnicke> )
15:52:56 <prasanna> #link dry run https://jenkins.opendaylight.org/openflowplugin/job/openflowplugin-bulk-release-prepare-only/7/
15:54:29 <regXboi> who wrote the original of the version check job?
15:54:59 <colindixon> I think that was Madhu or cdub
15:55:31 <Madhu> original from Gmeo in Controller
15:55:49 <regXboi> ok... will go find him
15:58:52 <edwarnicke> So I have good news and bad news
15:59:06 <edwarnicke> The good news is that I see release artifacts from yangtools in nexus
15:59:14 <edwarnicke> And I see the new snapshot version in their repo
15:59:17 <edwarnicke> So release was successful
15:59:38 <edwarnicke> The bad news is https://jenkins.opendaylight.org/controller/job/controller-yangtools-integration/245/ evidently the last yangtools patch broke controller, and will thus need to be reverted
15:59:46 <edwarnicke> rovarga: Would you please revert the last yangtools patch
15:59:52 <rovarga> will do
15:59:54 <edwarnicke> And then we can step through to release
16:00:02 <edwarnicke> rerelease that is
16:01:46 <rovarga> the revert is verifying
16:03:34 <edwarnicke> link?
16:03:46 <edwarnicke> For both the Gerrit and verify job?
16:03:53 <rovarga> #link https://jenkins.opendaylight.org/yangtools/job/yangtools-verify/603/
16:04:00 <rovarga> #link https://git.opendaylight.org/gerrit/#/c/4894/
16:04:27 <prasanna> #link release job https://jenkins.opendaylight.org/openflowplugin/job/openflowplugin-bulk-release-prepare-only/configure please verify
16:04:34 <regXboi> Madhu - what was the fix on the dry-run problem?
16:04:39 <regXboi> I don't think I saw that memo either
16:06:20 <edwarnicke> prasanna: Remove the pre-step to excute the shell
16:06:45 <prasanna> ok
16:06:47 <edwarnicke> regXboi: hideyuki discovered how to do a dryrun all the way through in the presence of SNAPSHOT
16:06:58 * edwarnicke cannot begin to express how much hideyuki saved us
16:07:08 <regXboi> that's not the problem I'm referring to
16:07:33 <regXboi> I'm referring to git-tag blowing up on .git not being a repository or any of the parent directories
16:07:52 <edwarnicke> tykeal: Could you help... sounds like it may be a permissions issue
16:07:57 <rovarga> verify completed
16:08:03 <prasanna> #link https://jenkins.opendaylight.org/openflowplugin/job/openflowplugin-bulk-release-prepare-only/configure
16:08:31 <rovarga> #link merge job for the yangtools revert https://jenkins.opendaylight.org/yangtools/job/yangtools-merge/374/
16:09:44 <GiovanniMeo> regXboi
16:09:48 <GiovanniMeo> i know what is the issue
16:09:49 <GiovanniMeo> there
16:09:54 <tykeal> edwarnicke: it's not a permission issue, it's that the release plugin is stepping up out of the git repo before it tries to run the tag operation
16:10:02 <GiovanniMeo> or at least i know what could be
16:10:06 <GiovanniMeo> i fixed on OVSDB
16:10:08 <GiovanniMeo> similar issue
16:10:13 <tykeal> there's been a few folks that have had this issue, but I don't know the fix
16:10:13 <regXboi> ok, how?
16:10:18 <edwarnicke> GiovanniMeo !
16:10:20 <GiovanniMeo> one second
16:10:42 * regXboi feels like the "stick-in-the-mud" at the party
16:10:43 <GiovanniMeo> https://git.opendaylight.org/gerrit/#/c/4763/
16:10:45 <edwarnicke> GiovanniMeo: Would you be willing to look over folks release jobs, as you know it better than I do?
16:10:58 <GiovanniMeo> sorry Ed still in a session
16:11:04 <GiovanniMeo> so i will be on and off
16:11:15 <edwarnicke> GiovanniMeo: ACK
16:11:21 <GiovanniMeo> i just couldn't stop to answer to regXboi
16:11:28 <GiovanniMeo> given i already ran into it
16:11:34 <regXboi> ok... let me give that a shot
16:12:25 <edwarnicke> Christine_: I think you were seeing this issue too, correct?
16:12:31 <GiovanniMeo> regXboi
16:12:38 <regXboi> yes?
16:12:39 <GiovanniMeo> the fix should be applicable to your case too
16:12:51 <GiovanniMeo> i just looked at your release pom
16:12:55 <GiovanniMeo> misisng parent
16:12:59 <GiovanniMeo> i can explain why the issue
16:13:00 <regXboi> yes... I can do that
16:13:25 <Christine_> edwarnicke: seeing now...
16:13:26 <GiovanniMeo> but it's a logic in the maven-release-plugin that is causing a wrong computation
16:13:36 <GiovanniMeo> and so the git push tag
16:13:42 <GiovanniMeo> is going off the git repository
16:15:12 <regXboi> I'm concerned about the artifactId and relativePath that I need to use
16:16:58 <prasanna> Should OF plugin wait till "controller" and "Library" complete the release job?
16:17:14 <Madhu> prasanna: ye
16:17:15 <Madhu> yes
16:17:25 <prasanna> ok |Thanks Madhu
16:17:42 <Madhu> regXboi: sorry. am back. anything i can help ?
16:17:49 <Madhu> i see GiovanniMeo is active :)
16:18:22 <regXboi> well, I'm fighting with setting the parent in the opendove release pom properly
16:18:40 <regXboi> because I'm not coming up with anything that will build (so far)
16:18:51 <edwarnicke> Ran controller change versions here: https://jenkins.opendaylight.org/controller/job/controller-version-changes/13/
16:18:57 <Madhu> regXboi: yes
16:19:03 <Madhu> https://git.opendaylight.org/gerrit/#/c/4763/ solved the problem for ovsdb
16:19:09 <edwarnicke> Need to find out why it didn't change any versions to match the changes in yangtools snapshots
16:19:17 <regXboi> yes, but something similar isn't working for opendove
16:21:02 <regXboi> Madhu: side channel question - I may have fixed the issue
16:21:12 <rovarga> the merge job has finished, btw
16:21:19 <Madhu> edwarnicke: u want the version changes to be snapshots or release version of yang tools ?
16:21:28 <edwarnicke> tykeal cdub Could you take a look at: https://jenkins.opendaylight.org/controller/job/controller-version-changes/13/ and see if you see anything about why it isn't pushing a Gerrit ?
16:21:45 * cdub looks
16:21:48 <edwarnicke> Madhu: We need the new yangtools snapshots to do an integration verification
16:21:53 <edwarnicke> 0.6.1-SNAPSHOT
16:22:02 <tykeal> I'll take a peak
16:22:12 <regXboi> whiskey tango foxtrot?
16:23:32 <networkstatic> lolz
16:23:33 <rovarga> #info prepare-only job for yangtools-0.6.1 is running at https://jenkins.opendaylight.org/yangtools/job/yangtools-bulk-release-prepare-only/14/
16:23:36 <edwarnicke> I think the reasons was because I fired the version change job before the artifacts were pushed from yangtools from its merge job
16:24:31 <tykeal> probably... I see that #14 caused a commit
16:24:39 <tykeal> at least that's what the bot just said a moment ago ;)
16:25:02 <rovarga> edwarnicke: it should have shown you the released artifacts, right?
16:25:25 <Christine_> edwarnicke: snmp4sdn already had the setting as https://git.opendaylight.org/gerrit/#/c/4763/  GiovanniMeo gave
16:25:43 <edwarnicke> #link https://jenkins.opendaylight.org/controller/job/controller-version-changes/15/console we have got updated versions
16:25:47 <edwarnicke> verify jobs running on them
16:26:04 <GiovanniMeo> tykeal
16:26:07 <tykeal> yes?
16:26:07 <GiovanniMeo> #14
16:26:08 <regXboi> question: who has a link to how to configure the checkstyle plugin?
16:26:10 <GiovanniMeo> cause commits
16:26:15 <GiovanniMeo> but just on a branch
16:26:19 <GiovanniMeo> that can be disposed
16:26:52 <Konstantin_> Request to interject: Defense4all current version is RELEASE already. So, release job will fail (“You don't have a SNAPSHOT project in the reactor projects list.” )
16:26:59 <edwarnicke> Quick summary of where we are in the process, because I know folks are also doing a lot of good debugging inline as well
16:27:06 <rovarga> #link controller checking whether yangtools have been fixed by the revert runs at https://jenkins.opendaylight.org/controller/job/controller-verify/3338/
16:27:08 <Konstantin_> Should we just skip this step and mark current version as cutoff RELEASE ?
16:27:51 <edwarnicke> yangtools released.  Its last patch broke controller.  yangtools has reverted the patch.  Controller is updating to the new snapshot.  Once that is confirmed good, yangtools will release again, and then its controllers turn :)
16:28:07 <colindixon> Madhu, edwarnicke: if you have a sec to help regXboi with checkstyle that'd be great
16:28:21 <edwarnicke> Konstantin_: I believe we talked about this... you guys are just hitting rest, and so somewhat  of a special case
16:28:26 <regXboi> n/m think I found it
16:28:28 <edwarnicke> I think mostly you just need to rerun your testing against the release
16:28:33 <edwarnicke> Once we get there
16:28:37 <edwarnicke> To make sure you are good :)
16:28:59 <Konstantin_> Ok, waiting for controller for test. Last build we tested was yesterday.
16:29:19 <edwarnicke> Konstantin_: Excellent :)
16:30:01 <Madhu> edwarnicke: got it.
16:30:12 <Madhu> so .... we have 2 releases of yang tools ?
16:30:15 <suchiraman> #link affinity release-prepare-only is here: https://jenkins.opendaylight.org/affinity/job/affinity-bulk-release-prepare-only/
16:30:26 <Madhu> and the final dependency will be 0.6.1 RELEASE ?
16:30:32 <rovarga> Madhu: yes
16:30:44 <Madhu> thanks rovarga
16:31:02 <Madhu> colindixon: i will ping him
16:31:32 <colindixon> Madhu: thanks! I think he's making progress, but always to check in
16:31:51 <edwarnicke> Madhu: We had to respin yangtools,yes
16:32:03 <edwarnicke> Madhu: Should be, yes
16:32:13 <cdub> tykeal: you see anything re: gerrit?
16:32:15 <edwarnicke> Madhu: Should be 0.6.1 yes
16:32:31 <Madhu> thanks. just confirming guys.
16:32:43 <tykeal> cdub: see edwarnicke's comment about probably firing the job too early
16:32:52 <cdub> tykeal: yeah, saw that, ok
16:33:50 <colindixon> #info there are two release versions for yangtools as a result of a last minute revert, but the *correct* final dependency for yangtools should be 0.6.1 RELEASE
16:33:54 <colindixon> for posterity
16:34:00 <edwarnicke> colindixon: Thank you :)
16:36:17 <edwarnicke> Would everyone who depends on yangtools please run their version change job and make sure the resulting patch verifies
16:37:38 <hideyuki> Which version should we use for jersey, 1.17 or 1.18?
16:38:00 <edwarnicke> Madhu: Do you know?
16:38:04 <GiovanniMeo> 1.17
16:38:13 <edwarnicke> cdub: Do you know which version of jersey?
16:38:13 <hideyuki> In controller git repo, third-party/jersey-servlet/pom.xml use 1.18-SNAPSHOT now.
16:38:14 <GiovanniMeo> 1.18 will not be geenerated
16:38:24 <GiovanniMeo> that is not part of the build
16:38:28 <GiovanniMeo> it was disabled
16:38:31 <GiovanniMeo> long time ago
16:38:36 <GiovanniMeo> and yes
16:38:37 <edwarnicke> concur with GiovanniMeo on this
16:38:47 <GiovanniMeo> i know the version-changes
16:38:49 <Madhu> hideyuki: we migrated to jersey 2.3.0
16:39:06 <Madhu> and we pushed a patch to VTN a long time back
16:39:24 <Madhu> ooops sorry guys
16:39:27 <Madhu> i meant jackson
16:39:30 <regXboi> uh, really?
16:39:38 * Madhu shud get some sleep
16:39:42 <GiovanniMeo> Madhu is there a jersey-servlet needed with 2.3.0?
16:39:56 <GiovanniMeo> the reason for 1.17-SNAPSHOT
16:39:58 <hideyuki> how about net.sf.jung2?
16:40:03 <GiovanniMeo> was because the jersey out of the box
16:40:16 <edwarnicke> For everyone who just ran a version change job.  Please #link your resulting Gerrit and verify Jenkins Job
16:40:26 <GiovanniMeo> ok
16:40:39 <hideyuki> 2.0.1? or 2.0.2 for net.sf.jung2?
16:41:02 <GiovanniMeo> #info for all jersey-servlet should be at 1.17
16:41:08 <regXboi> um
16:41:41 <regXboi> the version update slams it to 1.1.8
16:41:43 <regXboi> er 1.18 that is
16:41:46 <GiovanniMeo> #info net.sf.jung 2.0.1
16:41:55 <GiovanniMeo> regXboi
16:41:57 <GiovanniMeo> yes i know
16:42:01 <hideyuki> GiovanniMeo: ok, thank you.
16:42:09 <GiovanniMeo> just force it to 1.17
16:42:14 <GiovanniMeo> i can explain the dynamic
16:42:19 <regXboi> wonderful
16:42:21 <cdub> i compared against 2.0.1 (and 1.17 for jersey-servlet)
16:42:27 <Christine_> https://jenkins.opendaylight.org/snmp4sdn/job/snmp4sdn-bulk-release/ works now (with IGNORE_SNAPSHOTS used), thanks to GiovanniMeo's help :)
16:42:37 <regXboi> no worries... gotta fix that then
16:42:58 <GiovanniMeo> you want me to explain now
16:43:06 <GiovanniMeo> else will take offline
16:43:07 <regXboi> don't need it
16:43:15 <regXboi> just need to know that I have to change
16:43:15 <GiovanniMeo> don't want to flood the channel
16:43:23 <GiovanniMeo> with silly technical explanations
16:43:50 <regXboi> so 1.17 or 1.17-SNAPSHOT?
16:45:14 <edwarnicke> OK... it seems that version change is not correctly picking up variables set in a parent pom that are not used in the parent pom: http://stackoverflow.com/questions/3628471/maven-versions-plugin-not-picking-up-properties-from-parent
16:45:45 <hideyuki> regXboi: For release artifacts, jersey 1.17.
16:46:25 <regXboi> hideyuki: that doesn't quite answer my question
16:48:19 <edwarnicke> OK... for those who depend on yangtools
16:48:28 <edwarnicke> Looks like the version change job is not reliable
16:48:54 <edwarnicke> Please run
16:48:54 <edwarnicke> grep -r --include=pom.xml 0.6.0-SNAPSHOT .
16:49:16 <edwarnicke> And investigage and push a manual update to 0.6.1-SNAPSHOT
16:49:51 <rovarga> edwarnicke: not only that
16:50:06 <rovarga> there are also models which have different versioning schema :-/
16:51:47 <colindixon> rovarga: ugh
16:52:58 <rovarga> the reason is that their versions are derived from the yang revision they hold + a "spin" version
16:53:13 <rovarga> that spin is bumped by the release plugin just fine
16:53:15 <GiovanniMeo> regXboi
16:53:20 <GiovanniMeo> not -SNAPSHOT
16:53:23 <GiovanniMeo> the gist is
16:53:27 <GiovanniMeo> between project
16:53:33 <GiovanniMeo> no SNAPSHOT dependencies
16:53:33 <regXboi> got it
16:53:40 <regXboi> trying to get this patch to commit
16:55:24 <rovarga> affinity guys: you are still running on 0.5.9-SNAPSHOT of yangtools and down-revved models
16:55:51 <rovarga> at least your master is ...
16:58:52 <Konstantin_> b
16:59:21 <edwarnicke> working on updating controller manually
17:02:38 <regXboi> ok folks, I need some pom help on the side
17:03:00 <regXboi> I'm running into maven issues with trying to put in the parent information to fix the dry-run bug
17:03:04 <regXboi> who can I ping?
17:03:46 <suchiraman> offline for 20 mins
17:08:21 <GiovanniMeo> regXboi
17:08:28 <GiovanniMeo> i'll take care of it
17:08:32 <edwarnicke> #link https://git.opendaylight.org/gerrit/#/c/4909/ - change of yangtools version to 0.6.1-SNAPSHOT
17:08:32 <GiovanniMeo> taking offline
17:08:34 <edwarnicke> Now to do the models
17:08:37 <regXboi> ok...
17:09:25 <edwarnicke> Here are the model versions to track down
17:09:33 <edwarnicke> https://www.irccloud.com/pastebin/bLeTzfBv
17:10:07 <colindixon> SNAPSHOT or RELEASE?
17:11:04 <rovarga> grepping for these and changing them to +1-SNAPSHOT will bring you inline with 0.6.1-SNAPSHOT of yangtools
17:13:53 <GiovanniMeo> Ed instead of changing manually
17:13:58 <GiovanniMeo> we can run the version-changes
17:14:03 <GiovanniMeo> but remove the flag
17:14:04 <edwarnicke> GiovanniMeo: Version changes failed
17:14:06 <edwarnicke> Miserably
17:14:14 <edwarnicke> Missed *most* of the cases that needed updating
17:14:17 <GiovanniMeo> that says allowSnapshots
17:14:33 <edwarnicke> Turns out, if you declare a version variable in a pom that it does not use it
17:14:37 <GiovanniMeo> is it in jenkins?
17:14:38 <edwarnicke> It fails
17:14:50 <edwarnicke> http://stackoverflow.com/questions/3628471/maven-versions-plugin-not-picking-up-properties-from-parent
17:15:07 <GiovanniMeo> ok one second
17:15:13 <GiovanniMeo> NMI on other line
17:16:48 <edwarnicke> #link https://git.opendaylight.org/gerrit/#/c/4909/ - fixed yangtools version dependencies
17:17:25 <edwarnicke> rovarga: Please review https://git.opendaylight.org/gerrit/#/c/4909/ and see if it looks right to you
17:18:07 <edwarnicke> goldavberg: How are you doing on fixing your versions?
17:18:26 <edwarnicke> suchiraman: How are you doing on fixing your versions?
17:19:47 <rovarga> edwarnicke: just a second
17:21:48 <rovarga> looks good
17:21:57 <goldavberg> edwarnicke: i updated the yang versions and merged it
17:22:59 <goldavberg> but maybe i have other artifacts with versions which are not up to date
17:24:03 <NLNils> edwarnicke: am checking for you
17:24:16 <suchiraman> Moving to 0.6.1 yangtools in affinity repo
17:26:33 <oflibMichal> openflowjava will push and merge yangtools related changes after successful release - there are no integration tests between yangtools and openflowjava/openflowplugin
17:26:49 <oflibMichal> hope it is ok for everyone
17:27:44 <cdub> edwarnicke: yangtools (internally) isn't completely moved yet, unless i'm missing an outstanding review or looking at wrong branch
17:27:54 <edwarnicke> oflibMichal: Please change now and check
17:27:59 <edwarnicke> I don't want to have to go back and do this again
17:28:09 <edwarnicke> michal_rehak: Please change openflowplugin and check
17:28:12 <oflibMichal> edwarnicke: ok
17:28:14 <edwarnicke> I don't want to have to do this again
17:28:15 <goldavberg> edwarnicke: lispflowmapping is fully updated
17:28:24 <regXboi> when people get free, I need serious help - I've managed to break opendove completely trying to fix the dry run issue
17:28:34 <regXboi> none of the jenkins jobs work at this point
17:28:42 <regXboi> well verify and merge don't
17:30:27 <edwarnicke> regXboi: Will help you as soon as we get yangtools out and start controller moving
17:30:43 <edwarnicke> regXboi: The good news is, through the magic of git all mistakes are revertable
17:30:44 <regXboi> ok, I have to do a phone call now, so won't be completely reading
17:30:56 <edwarnicke> goldavberg: Thank you :)
17:33:50 <edwarnicke> goldavberg: Did you check for the model versions as well?
17:34:55 <goldavberg> edwarnicke: we haven't used variables for the models versions so they are updated
17:36:14 <michal_rehak> edwarnicke: in ofplugin  - yangtools exist only in sample-consumer
17:36:44 <edwarnicke> goldavberg: Here is the omnibus grep pipeline (you pass it by the way):
17:36:45 <edwarnicke> grep -r --include=pom.xml clustered-data .;grep -r --include=pom.xml 2013.07.04.2 .;grep -r --include=pom.xml 2013.10.21.0 .;grep -r --include=pom.xml 2013.10.21.0 .;grep -r --include=pom.xml 2013.10.21.0 .;grep -r --include=pom.xml 2010.09.24.2 .;grep -r --include=pom.xml 2013.07.04.2 .1567;grep -r --include=pom.xml 2013.07.04.2 .1571
17:37:05 <edwarnicke> Oops... the clustered-data bit at the front is wrong
17:39:13 <edwarnicke> Madhu: Please review and merge: https://git.opendaylight.org/gerrit/#/c/4909/ (note: GiovanniMeo comment is not applicable here because we are respining to a new SNAPSHOT, not yet releases.
17:39:44 <GiovanniMeo> ?
17:39:48 <GiovanniMeo> sorry yangtools
17:39:53 <GiovanniMeo> did release 0.6.1
17:39:54 <GiovanniMeo> right?
17:40:00 <edwarnicke> Nope
17:40:01 <GiovanniMeo> so they are done
17:40:04 <edwarnicke> it did release 0.6.0
17:40:05 <edwarnicke> Which broek
17:40:10 <cdub> they are on 0.6.1-SNAPSHOT
17:40:10 <edwarnicke> So we reverted a patch
17:40:13 <edwarnicke> And are respinning
17:40:22 <GiovanniMeo> so eventually will get to 0.6.1
17:40:26 <edwarnicke> Yes
17:40:29 <GiovanniMeo> so better to wait till them are done
17:40:35 <GiovanniMeo> and just submit to 0.6.1
17:40:46 <edwarnicke> First we have to make sure 0.6.1-SNAPSHOT *works*
17:40:55 <GiovanniMeo> not really
17:40:57 <edwarnicke> And that the dry run still works
17:41:00 <GiovanniMeo> you can just test with 0.6.1
17:41:34 <edwarnicke> And then if there is a problem we have to respin again?
17:42:47 <edwarnicke> suchiraman: Are you guys good with 0.6.1-SNAPSHOT
17:42:54 <edwarnicke> michal_rehak: Are you good with 0.6.1-SNAPSHOT
17:42:58 <GiovanniMeo> Ed
17:43:02 <edwarnicke> oflibMichal: Are you good with 0.6.1-SNAPSHOT
17:43:06 <GiovanniMeo> you have anyway to respin
17:43:15 <oflibMichal> on the way to merge
17:43:16 <edwarnicke> GiovanniMeo: I am seeking to avoid a 0.6.2 today
17:43:19 <oflibMichal> eta 3 mins
17:43:26 <GiovanniMeo> Ed
17:43:36 <GiovanniMeo> 0.6.1 is the dependencies in controller
17:43:45 <edwarnicke> GiovanniMeo: There is no 0.6.1 yet
17:43:46 <GiovanniMeo> hence is the final goal in controller
17:43:49 <edwarnicke> It hasn't been released
17:43:52 <GiovanniMeo> yes
17:43:56 <GiovanniMeo> wait for them
17:43:58 <GiovanniMeo> to generate
17:44:01 <GiovanniMeo> push the controller
17:44:02 <edwarnicke> And it won't be released till we know it *works* downstream
17:44:03 <GiovanniMeo> to 0.6.1
17:44:04 <suchiraman> edw: yes 0.6.1 is checked in.
17:44:05 <GiovanniMeo> if you are done
17:44:14 <GiovanniMeo> then you are fine
17:44:15 <edwarnicke> suchiraman: You mean 0.6.1-SNAPSHOT?
17:44:21 <edwarnicke> suchiraman: Did you check for the models as well?
17:44:50 <edwarnicke> GiovanniMeo: And if we aren't fine, then we have to spin a 0.6.2... this way, we know 0.6.1-SNAPSHOT is fine, and so we know when we release 0.6.1 it is fine
17:44:51 <suchiraman> edw: Yes 0.6.1-SNAPSHOT. I have datestamps for models.
17:45:00 <edwarnicke> suchiraman: Thank you :)
17:46:16 <GiovanniMeo> 0.6.1 must anyway be generated to know it's not good
17:47:28 <rovarga> GiovanniMeo: it will be
17:47:41 <rovarga> but we need to verify that IT failure has been completed
17:47:42 <edwarnicke> GiovanniMeo: 0.6.1 will be the same source as this 0.6.1-SNAPSHOT
17:47:44 <rovarga> fixed
17:47:54 <GiovanniMeo> of course
17:48:02 <GiovanniMeo> so you can cut a step and test with 0.6.1
17:49:08 <edwarnicke> And then if 0.6.1 has a problem, we go back to the beginning and start over with 0.6.2-SNAPSHOT... which is what I am seeking to avoid
17:49:37 <GiovanniMeo> you have to go to 0.6.2 anyway
17:49:39 <GiovanniMeo> if 0.6.1
17:49:41 <GiovanniMeo> is bad
17:49:44 <rovarga> no I don't
17:50:03 <GiovanniMeo> you don't need to do any step anymore on -SNAPSHOT
17:50:06 <rovarga> because we have to releaseed 0.6.1, so we can merge a patch and just retrigger merge job
17:50:17 <edwarnicke> GiovanniMeo: If 0.6.1-SNAPSHOT is bad. Then we simply fix it.  Everybody rebuilds.  Nobody changes files.
17:50:20 <rovarga> *have not released
17:50:20 <GiovanniMeo> sure thanks rovarga
17:50:38 <edwarnicke> If we jump to 0.6.1 and its bad.  Everyone has to edit files for 0.6.2.  Verifies have to run. etc
17:50:54 <edwarnicke> Better to check SNAPSHOT and make sure its right
17:51:55 <oflibMichal> edwarnicke: openflowjava - yangtools version update done
17:52:09 <edwarnicke> Thank you
17:52:22 <edwarnicke> michal_rehak: Where are we on openflowplugin?
17:52:42 <michal_rehak> ofplugin - https://git.opendaylight.org/gerrit/#/c/4913/
17:53:49 <edwarnicke> So as soon as  https://git.opendaylight.org/gerrit/#/c/4913/ verifies we can cut yangtools 0.6.1
17:56:03 <Madhu> sorry guys. back.
17:56:17 <Madhu> so we will manually move to Yangtools 0.6.1
17:56:33 <Madhu> and a build check alone ? or requires runtime validation ?
17:58:38 <michal_rehak> ofplugin : merged
18:00:19 <edwarnicke> Madhu: We have almost finished checking out 0.6.1-SNAPSHOT
18:00:29 <edwarnicke> In fact... michal_rehak is the last report
18:00:36 <edwarnicke> So I believe we can now cut 0.6.1 yangtools
18:00:44 <Madhu> i just updated 0.6.1 in ovsdb
18:00:46 <edwarnicke> rovarga: Shall you do the honors?
18:00:48 <Madhu> snapshot
18:00:52 <edwarnicke> Ah
18:00:57 <edwarnicke> Does it build?
18:00:59 <Madhu> just build check will do ?
18:01:00 <edwarnicke> rovarga: One moment
18:01:07 <Madhu> yep. it built locally
18:01:10 <Madhu> i will push it now
18:01:11 <edwarnicke> OK
18:01:23 <edwarnicke> rovarga: Please proceed to cut 0.6.1 yangtools :)
18:02:36 <rovarga> gladly
18:02:56 <edwarnicke> Thank you :)
18:03:01 <rovarga> #link yangtools-0.6.1 release job is over at https://jenkins.opendaylight.org/yangtools/job/yangtools-bulk-release/2/
18:03:02 <edwarnicke> Please #link as relavent
18:03:03 <edwarnicke> :)
18:03:52 <rovarga> ETA 16 minutes
18:04:11 <cdub> edwarnicke: is master the right branch to look at for yangtools?
18:04:22 <rovarga> cdub: yes
18:04:55 <cdub> rovarga: ok, when i looked a few minutes ago, it was still not internally aligned to 0.6.1-SNAPSHOT
18:05:22 <rovarga> cdub: master of which project?
18:05:28 <cdub> rovarga: yangtools
18:06:23 <rovarga> the only non-bumped artifacts are those which are not being built
18:06:48 <cdub> e.g. models?
18:07:39 <rovarga> model parent is definitely on 0.6.1-SNAPSHOT on current yangtools master
18:08:08 <rovarga> models themselves follow a yang-revision-based versioning scheme
18:08:15 <rovarga> and that has been updated as well
18:08:26 <cdub> rovarga: look at, for model/ietf/ietf-netconf/pom.xml
18:08:47 <cdub> for example.  parent is:
18:08:47 <rovarga> ietf-netconf is not part of yangtools reactor
18:08:47 <cdub> <groupId>org.opendaylight.yangtools.model</groupId>
18:08:47 <cdub> <version>0.6.0-SNAPSHOT</version>
18:09:13 <rovarga> model/ietf.pom.xml lists it as:
18:09:16 <rovarga> <!--module>ietf-netconf</module -->
18:09:24 <cdub> ah, yes...thank you
18:11:16 <cdub> rovarga: and any reason restconf-parent is on a different numbering schemem (0.6.0)?
18:13:19 <rovarga> cdub: can you re-state that question?
18:14:04 <cdub> rovarga: is there any reason restconf-parent is 0.6.0-SNAPSHOT instead of 0.6.1-SNAPSHOT like the rest of the yangtools project?
18:14:29 <rovarga> nite@nitebug ~/odl/yangtools $ git log | head -n 1
18:14:30 <rovarga> commit 1a1957d95316cb48d5dc49960ec7b8668321c2ae
18:14:49 <cdub> same here
18:15:14 <rovarga> restconf/pom.xml lists yangtools-0.6.1-SNAPSHOT as its parent
18:15:19 <rovarga> and has no explicit version tag
18:15:23 <rovarga> e.g. is 0.6.1-SNAPSHOT
18:16:34 <rovarga> nite@nitebug ~/odl/yangtools $ find . -name pom.xml | xargs fgrep 0.6.0-SNAPSHOT
18:16:36 <cdub> sorry, s/parent/common/
18:17:00 <rovarga> results in 7 lines, none of which are part of the release
18:17:03 <cdub> and aapears to also not get pulled into build
18:17:42 <rovarga> these things is stuff which we have in the repository, but are not ready for release
18:17:45 <cdub> thanks, sorry for distractions
18:17:47 <rovarga> so we are not building them
18:17:52 <rovarga> and we do not release them
18:18:23 <rovarga> np. :)
18:19:22 <edwarnicke> cdub: Thank you for your vigilance :)
18:19:32 <edwarnicke> Its much appreciated :)
18:19:45 <cdub> heh, you're welcome
18:20:59 <rovarga> #info yangtools release 0.6.1 has been pushed into nexus
18:23:55 <edwarnicke> rovarga: Could you check the source code on master for yangtools ?
18:25:04 <cdub> fwiw, i just checked yangtools src (master branch), and it's all -> 0.6.1 -> 0.6.2-SNAPSHOT
18:25:25 <edwarnicke> cdub: Thanks :)
18:25:27 <cdub> (not sure if that's what you were interested in...)
18:25:30 <rovarga> commit fbda975368dc4401ba0eda8a98ec2ed88f6e0621 shows no pom.xml referencing the string "0.6.1"
18:26:09 <edwarnicke> I'm starting working to update the controller
18:26:19 <edwarnicke> I'm going to let version change do as much of the work as it can
18:26:20 <regXboi> tykeal: Ping?
18:26:25 <tykeal> regXboi: pong
18:26:28 <edwarnicke> Then amend it with the fixes that have to be done manually
18:26:30 <rovarga> model revisions seem to have been bumped, too
18:28:25 <rovarga> #info https://jenkins.opendaylight.org/bgpcep/job/bgpcep-verify/1386/ is verifying bgpcep's use of the released yangtools artifacts
18:29:36 <edwarnicke> #link https://git.opendaylight.org/gerrit/#/c/4921/ result of version change... let me fix it up where needed and we'll be off to the races :)
18:40:59 <edwarnicke> FYI... I'm through the yangtools part... checking the models
18:41:36 <cdub> edwarnicke: i think there's more than in the commit
18:41:46 <oflibMichal> I am leaving the office now, I will be back in about 30 minutes
18:41:55 <edwarnicke> cdub: Absolutely
18:42:02 <edwarnicke> cdub: change version is a nice start
18:42:05 <edwarnicke> But its not complete
18:42:11 <cdub> edwarnicke: ok, i see a couple straight away
18:42:32 <cdub> i'll wait until you do a pass-n-update
18:42:52 <edwarnicke> rovarga: What is the correct version for 2013.10.21.0 ?
18:42:57 <edwarnicke> cdub: Thank you :)
18:43:40 <rovarga> 2013.10.21.1
18:44:19 <cdub> crud...too many overlapping mtgs this AM
18:44:22 <edwarnicke> And 2013.08.27.3 is correct?
18:45:01 <rovarga> I need to look that up :)
18:45:09 <edwarnicke> Please do :)
18:45:41 <rovarga> edwarnicke: yes
18:45:52 <rovarga> opendaylight-l2-types 2013.08.27.3
18:46:02 <rovarga> yang-ext 2013.09.07.3
18:46:18 <rovarga> ietf-inet-types 2010.09.24.3
18:46:30 <rovarga> ietf-yang-types 2010.09.24.3
18:46:55 <rovarga> the various ietf-topology bits 2013.10.21.1
18:47:22 <rovarga> iana-afn-safi and iana-if-type 2013.07.04.3
18:47:35 <edwarnicke> ietf-topology-l3-unicast-igp ?
18:47:58 <rovarga> 2013.10.21.1
18:48:24 <rovarga> ietf-ted  ietf-topology  ietf-topology-isis  ietf-topology-l3-unicast-igp  ietf-topology-ospf are all  2013.10.21.1
18:51:00 <colindixon> can somebody with more familiarity with nexus repos than regXboi and I take a look at the last erorr here: https://jenkins.opendaylight.org/opendove/job/opendove-verify/134/console
18:51:49 <colindixon> I thought we had removed all references to the opendaylight-release repository, but it's still seeming to look for artifacts there and then failing
18:52:47 <regXboi> ah... I may have found it colindixon
18:53:36 <colindixon> also, it would be useful if anyone knows how to reproduce this kind of thing locally, because mine failed the same way as jenkins is claiming the first time, but has succeeded each time after that despite continuing to fail on jenkins
18:54:12 <regXboi> I found what is causing things to break
18:54:25 <regXboi> now, what is causing that to happen is the next question
18:56:07 <regXboi> because I thought packing of bundle published both the jar and the pom
18:56:45 <rovarga> your odmc/pom.xml should be packaging=pom
18:57:05 <rovarga> I guess
18:57:12 <regXboi> no, it's been bundle since day one
18:57:14 <rovarga> err... disregard that
18:57:24 <regXboi> I tried changing it to pom and that's what started this insanity
18:57:34 <regXboi> and now I can't get jenkins/gerrit/git to let me put it back
19:00:57 <edwarnicke> #link https://git.opendaylight.org/gerrit/#/c/4921/ updated with manual fixes
19:01:25 <edwarnicke> Now we wait for the verify
19:04:52 <rovarga> #info bgpcep is using release artifacts of yangtools now
19:05:18 <edwarnicke> rovarga: Thank you :)
19:06:46 * rovarga will go offline for ~30 minutes
19:07:28 <hideyuki> edwarnicke: I think you submitted a wrong file "#pom.xml#" in https://git.opendaylight.org/gerrit/#/c/4921/
19:08:28 <edwarnicke> hideyuki: Good catch
19:08:30 <edwarnicke> Let me fix that
19:09:07 <hideyuki> edwarnicke: Ok. my colleague catched it :)
19:09:46 <edwarnicke> hideyuki: Fixed https://git.opendaylight.org/gerrit/#/c/4921/3
19:09:55 <edwarnicke> hideyuki: Please thank your colleague for me ;)
19:10:05 <hideyuki> edwarnicke: +1 for the patch.
19:11:21 <edwarnicke> Thank you :)
19:12:43 <regXboi> ok, with tykeal's help we've run down what was wrong with opendove jenkins, so now I can go back to looking at fixing the dry-run issue
19:12:59 <edwarnicke> tykeal: Many thanks
19:13:08 <edwarnicke> regXboi: As soon as I get controller out, I totally down to help you :)
19:13:09 <tykeal> sure
19:13:11 <regXboi> so, is there a place I can go look at a parent pom that I can copy from?
19:13:38 <regXboi> because that's all I need to apply GiovanniMeo's technique that worked for ovsdb
19:14:16 <edwarnicke> regXboi: link to where you are breaking down?
19:14:23 <edwarnicke> (I spent a lot of time fighting these demons this weekend)
19:20:01 <colindixon> where are we in terms of actually cutting artifacts?
19:20:01 <oflibMichal> hello, i am back
19:20:07 <oflibMichal> what is current status ?
19:20:15 <edwarnicke> colindixon: The patch for controller to update to yangtools is verifying
19:20:19 <edwarnicke> Then we do the controller release
19:20:36 <regXboi> edwarnicke: everything in jenkins is on the green
19:21:17 <regXboi> now, as I understand it, the fix for the dry-run is to specify a parent pom for the project so that git doesn't step outside
19:21:39 <regXboi> all I need is a parent pom to look at and copy from and I'm off and running
19:22:10 <cdub> edwarnicke: hmm, still looks like two lagging behind
19:22:49 <edwarnicke> cdub: Where?
19:22:52 <cdub> edwarnicke: which is easier for you, patch, cut'n paste, interpretive dance?
19:23:04 <edwarnicke> A patch would be welcome if you can do it as an amend
19:23:34 <edwarnicke> But I'll take whatever works
19:23:37 <cdub> heh
19:24:07 <cdub> maybe easier if I point it out and you amend
19:24:22 <edwarnicke> I'm down
19:24:43 <cdub> both are properties
19:25:04 <cdub> opendaylight/commons/opendaylight/pom.xml yangtools.version
19:25:17 <cdub> opendaylight/md-sal/pom.xml yangtools.version
19:26:11 <cdub> those seem to be the only causing skew right now
19:26:41 * cdub double checks...still failing..
19:27:11 <edwarnicke> :(
19:28:24 <cdub> oh...i see
19:28:28 <cdub> yes, that fixed
19:28:36 <cdub> now skew is -SNAPSHOT vs. release
19:28:46 <edwarnicke> ?
19:29:44 <edwarnicke> cdub: pointer on what needs to be fixed?
19:29:52 <cdub> i locally fixed w/ s/0.6.0-SNAPSHOT/0.6.1-SNAPSHOT/
19:29:59 <cdub> by mistake
19:30:05 <cdub> instead of s/0.6.0-SNAPSHOT/0.6.1/
19:30:26 <edwarnicke> Ah... I did 0.6.1 in the amend
19:30:33 <cdub> yeah
19:30:43 <cdub> so triggered the skew, i was half-step behind you
19:31:54 <edwarnicke> regXboi: It looks from your job like your issue is not the cutting of release versions or the building after that, but something missing that is borking the push to git, correct?
19:32:10 <regXboi> whoa ed
19:32:18 <regXboi> here's the problem stack:
19:32:27 <regXboi> (1) dry-run didn't work
19:32:38 <regXboi> (2) tried to fix #1 verify and merge didn't work
19:32:39 <edwarnicke> regXboi: Has dry-run ever worked?
19:32:41 <regXboi> no
19:32:54 <regXboi> but I'm trying to apply GiovanniMeo's fix now
19:33:02 <regXboi> so in a few I may be able to change that to yes
19:33:09 <regXboi> give me a few orbits :)
19:33:14 <edwarnicke> Let me know if you get stuck again
19:33:22 <regXboi> I'm real good at screaming
19:33:54 <edwarnicke> regXboi: Its one of the things we love about you
19:34:26 * regXboi decides to let that one just lie
19:34:27 <cdub> edwarnicke: i'll push the amended for review if you'd like.  i actually haven't done that on someone else's commit before...not sure what'll happen ;)
19:34:53 <edwarnicke> cdub: Just make sure to use --signoff and --author and you should be good
19:35:04 <cdub> i left you as author
19:35:13 <cdub> and just did SoB
19:36:06 <edwarnicke> Cool... I look forward to your patch
19:38:05 <regXboi> ok... let's see if this dry-run works
19:38:09 * regXboi crosses fingers
19:38:45 <cdub> edwarnicke: should be there now
19:39:26 <regXboi> edwarnicke: opendove dry-run now passes (finally)
19:40:40 <rovarga> still cutting yangtools?
19:40:45 <rovarga> e.g. new topic? :)
19:41:06 <cdub> rovarga: i guess we need a bigger saw
19:45:27 <colindixon> edwarnicke: where are we on controller?
19:46:09 <cdub> should be a test build happening right now with sync to yangtools released artifacts
19:46:23 <cdub> colindixon: https://git.opendaylight.org/gerrit/#/c/4921
19:46:49 * colindixon watches the paint dry
19:46:58 <edwarnicke> colindixon: Investigating
19:50:22 <cdub> Verified+1 Build Successful...
19:51:54 <edwarnicke> cdub: Still waiting for your patches crossing in the night patch to verify so Gerrit believes us
19:51:59 <edwarnicke> But as its identical in content to mine
19:52:02 <edwarnicke> It will
19:52:08 <edwarnicke> Then we can release controller :)
19:52:23 <edwarnicke> (well, there's merge and stuff in there too :) )
19:52:59 <cdub> if it doesn't...we'll need to talk to heisenberg
19:53:45 <edwarnicke> LOL
19:54:14 <edwarnicke> So... once the verify finishes, my thoughts are:
19:54:20 <edwarnicke> 1)  A controller committer merges it
19:54:26 <edwarnicke> 2)  We run dry-run
19:54:36 <edwarnicke> 3)  If dry-run succeeds we run release
19:55:19 <edwarnicke> #topic cutting controller
19:56:20 <michal_rehak> edwarnicke: patchset-5 verify is still running
19:56:34 <edwarnicke> michal_rehak: yep ;)
19:58:24 <edwarnicke> #link https://git.opendaylight.org/gerrit/#/c/4921/ verified
19:58:31 <michal_rehak> edwarnicke: ok, let's drink
19:58:32 <edwarnicke> Madhu: Would you review https://git.opendaylight.org/gerrit/#/c/4921/
19:58:45 <edwarnicke> michal_rehak: LOL... to early for that :)
19:58:45 <Madhu> edwarnicke: am on it
19:58:47 <cdub> michal_rehak: hehe, i like it
19:58:53 <cdub> michal_rehak: except it's before noon here ;)
19:59:01 <edwarnicke> (unless, like me, your drink of choice is Pellegrino sparkling water)
19:59:27 <michal_rehak> cdub: that's the advantage of distributed development - there is always evening somewhere
19:59:32 * cdub raises (tea) cup...
19:59:39 <cdub> michal_rehak: true
20:03:02 <Madhu> edwarnicke:  merged
20:03:14 <edwarnicke> Madhu: Thank you :)
20:03:25 <edwarnicke> Know I'll fire off dry run
20:04:01 <edwarnicke> with IGNORE_SNAPSHOTS=false
20:09:03 <colindixon> so, we're doing a (1) a dry run, (2) cut new snapshot, (3) update versions in all things depending on controller, (4) verify them, (5) cut release version of controller?
20:11:04 <cdub> sounds about right to me, except i think step 5 before 1.5
20:11:05 <edwarnicke> colindixon: Not quite
20:11:13 <cdub> s/before/becomes/
20:11:16 <edwarnicke> What cdub said
20:11:47 <edwarnicke> #1 #5 (#2 is a side effect of #5) #3 #4
20:11:56 <colindixon> got it
20:12:51 <edwarnicke> For those following along at home, the dry run is queued behind the merge job
20:12:55 <colindixon> (1) dry run for controller, (2) cut release version of controller, (3) update the version for all controller artifacts in all things depending on controller, (4) verify
20:13:09 <edwarnicke> tykeal: Any way we could move the dry run to a slave? (or would that be a bad idea for some reasons I don't understand)
20:13:27 <edwarnicke> colindixon: Yes, and then cut release versions of those dependent things
20:13:41 <tykeal> edwarnicke: just update the binding location from master to verify and it will move to one of the slaves
20:13:59 <colindixon> here's the merge job for those who like watching paint dry: https://jenkins.opendaylight.org/controller/job/controller-merge/1490/
20:14:04 <tykeal> the option is "only run on" or something like that near the top of the job definition
20:17:15 <edwarnicke> #link https://jenkins.opendaylight.org/controller/job/controller-bulk-release-prepare-only-2/ the dryrun job
20:19:24 <colindixon> how long about do these take?
20:20:07 <edwarnicke> For controller, about 20 minutes
20:20:10 <edwarnicke> For other things,usually less
20:21:40 <LuisGomez> edwarnicke: i believe we will need to update the pom files in the integration repo once you update the SNAPSHOT for the controller right?
20:21:55 <edwarnicke> Yes
20:22:21 <edwarnicke> I can help :)
20:22:37 <LuisGomez> ok, just making sure, this is the first time i see a release cut :)
20:23:09 <LuisGomez> i can do and you review or the other way around
20:24:33 <edwarnicke> We should try the change versions job first
20:24:38 <edwarnicke> And see if it gets it right
20:24:42 <edwarnicke> (hoping it does)
20:27:56 <LuisGomez> edwarnicke: change versions job in integration? i do not think this job is there...
20:28:18 <regXboi> are we just cutting maven artifacts today or are we also assembling the distro versions?
20:28:20 * edwarnicke looking
20:28:59 <colindixon> regXboi: the intent was to produce distros
20:29:20 <LuisGomez> edwarnicke: i can copy the job from some other place if needed
20:29:23 <edwarnicke> LuisGomez: Mind if I make one?
20:29:27 <edwarnicke> LuisGomez: Please do :)
20:29:35 <edwarnicke> Controller has one :)
20:29:50 <regXboi> um... well then I know ashaikh had some spec files for rpm generation for opendove components, but I don't know where they are in process
20:29:54 <regXboi> who can I ask?
20:30:36 <LuisGomez> edwarnicke: will do and let you know when done for u to review
20:31:41 <colindixon> merge just succeeded
20:32:03 <tykeal> regXboi: shague has been the point on spec files IIRC
20:32:21 <regXboi> that sounds right
20:32:35 <regXboi> ok... we'll see what we'll see
20:33:24 <edwarnicke> colindixon: dryrun is done... but merge is still going
20:33:37 <edwarnicke> Going to let merge finish so we are in a settled place in terms of published artifacts
20:33:40 <colindixon> merge just finished
20:33:50 <colindixon> [INFO] Deployment done in 1 min 28 sec
20:33:51 <colindixon> Sending e-mails to: controller-jenkins@lists.opendaylight.org
20:33:52 <colindixon> Finished: SUCCESS
20:34:27 * edwarnicke wanders off to fire the release job
20:34:54 <edwarnicke> #link https://jenkins.opendaylight.org/controller/job/controller-bulk-release-2/1/
20:35:46 <hideyuki> regXboi: do you have a plan to create a vm image including external apps of opendove and vtn for the Virtualization Edition?
20:36:00 <regXboi> do I have a plan?
20:36:14 <regXboi> not as such, no
20:36:20 <hideyuki> regXboi: ok.
20:36:39 <regXboi> I'm trying to make the rpms get built at this point
20:37:15 <regXboi> since for opendove at least, the piece parts end up living across multiple VMs and hosts
20:38:06 <hideyuki> regXboi: i see.
20:38:56 <colindixon> regXboi: there was a lot of discussion about maybe making a single VM that had all the stuff you might use
20:39:10 <colindixon> and then people could download it and spawn copies as they needed
20:39:45 <regXboi> not sure that makes sense when part of what's going on is kernel mods
20:39:55 <colindixon> edwarnicke: build #1 of anything is always scary
20:39:59 * colindixon crosses fingers
20:40:03 <colindixon> regXboi: yes
20:40:03 <edwarnicke> colindixon: Breath
20:40:12 <colindixon> that also came up
20:40:35 <colindixon> at which point, I think we need to produce our own VM image for that I think
20:40:49 <regXboi> going offline
20:41:01 <colindixon> kk
20:49:21 <RobDolin_> The fix for https://bugs.opendaylight.org/show_bug.cgi?id=380 was incomplete.  Alessandro, Vin, and I were just on IM and Alessandro submitted an updated fix.
20:51:07 <edwarnicke> RobDolin_: After the release :)
20:51:40 <Madhu> edwarnicke: if it is a low hanging, can't we take that ?
20:51:55 <Madhu> especially if it helps windows development
20:52:18 <edwarnicke> Madhu: Artifacts are actively cutting now
20:53:15 <RobDolin_> @EdWarnick - It's a one-line change (see the diff in https://bugs.opendaylight.org/show_bug.cgi?id=380)
20:56:49 <rovarga> please don't
20:57:03 <RobDolin_> @EdWarnicke - And without the fix the "Hello World" scenario of doing a pingall in Mininet is incomplete because the default flows don't get set-up.
20:58:18 <hideyuki> Are there any ways to avoid this problem without the patch?
21:00:15 <edwarnicke> Guys... artifacts are cutting as we speak
21:00:20 <LuisGomez> edwarnicke: i have created version changes job in integration: https://jenkins.opendaylight.org/integration/view/Integration%20jobs/job/integration-version-changes/
21:00:22 <rovarga> guys can we complete the cycle
21:00:26 <Madhu> edwarnicke: sorry for being stubborn here
21:00:32 <rovarga> and then perhaps go for a hotfix cycle?
21:00:36 <Madhu> but we did take this option today morning for yangtools
21:00:38 <Madhu> so how about
21:00:44 <Madhu> releasing a fix for switchmanager alone
21:00:58 <Madhu> and then use that as the official hydrogen version ?
21:00:59 <rovarga> we rereleased yangtools because they broke their upstream
21:01:04 <edwarnicke> Madhu: Yangtools was broken in a way that precluded releasing controller at all, and the only thing we did there was *revert* the breaking change
21:01:06 <Madhu> rovarga: yes
21:01:07 <rovarga> simply because there was no way forward
21:01:09 <Madhu> my point is
21:01:20 <Madhu> shall we re-release switchamanger alone ?
21:01:28 <Madhu> with the fix
21:01:32 <Madhu> let this continue and not stop it
21:01:39 <Madhu> once the release work is done for controller
21:01:46 <rovarga> had Ed noticed it 10 minutes earlier, we'd have reverted the patch and released 0.6.0 without it
21:01:47 <Madhu> lets release switch manager alone with this patch
21:01:56 <edwarnicke> Madhu: Note we did not *fix* the yangtools change, we simply reverted it
21:02:03 <Madhu> rovarga: sorry. i didn't mean to pin point that
21:02:12 <Madhu> just trying to help RobDolin_ with his request
21:02:15 <rovarga> Madhu: that's okay, it was our fault
21:02:15 <Madhu> which is legitimate
21:02:39 <Madhu> sure. i agree.
21:02:53 <Madhu> but we can certainly release just the switch manager after the release work on the controller
21:02:55 <Madhu> can't we ?
21:03:18 <Madhu> because we can do individual bundle releases as well
21:03:24 <Madhu> not necessarily bulk release
21:03:46 <colindixon> wouldn't we have to re-release everything that depended on switchmanager as well?
21:04:35 <edwarnicke> Guys... given all we've been through today to get to this point, And given the dependency tree issues that are complex due to controllers pom file organization, at this time, this would represent a giant risk of a large delay
21:04:41 <edwarnicke> We have an entire IRC full of folks
21:04:45 <edwarnicke> Who need to cut their own releases
21:04:55 <edwarnicke> Had this come in this morning before 9am PST
21:04:58 <edwarnicke> I would have been all over it
21:04:59 <cdub> hey, gives us a great opportunity to try out the -stable branch ;)
21:05:33 <rovarga> edwarnicke: +1
21:05:45 * cdub proposes first patch for stable branch is for switchmanager
21:06:11 <edwarnicke> cdub: Happy too :)
21:06:26 <Madhu> edwarnicke: u r the moderator :) your word is final. so I have to go with that
21:06:35 <RobDolin_> The bug was filed yesterday.
21:07:02 <colindixon> RobDolin_: I /want/ to take the patch incredibly badly
21:07:30 <colindixon> but, I'm with edwarnicke, that I just don't think we can take it now
21:14:38 <goldavberg> edwarnicke: how long before the controller finishes deploying its artifacts?
21:15:59 <edwarnicke> one moment
21:16:23 <colindixon> goldavberg: looks like it just finished
21:16:25 <colindixon> https://jenkins.opendaylight.org/controller/job/controller-bulk-release-2/1/
21:16:47 <colindixon> now *everyone* has to update versions
21:17:10 <edwarnicke> hang on
21:17:16 <edwarnicke> let me check things
21:18:47 <regXboi> unfortunately, I need to wander away soon...
21:18:52 <Konstantin_> Where can we download zip for our integration test ?
21:18:54 <edwarnicke> OK... I see the release artifacts in nexus... now checking the code
21:19:58 <edwarnicke> Konstantin_: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/controller/distribution.opendaylight/0.1.1/
21:20:14 <edwarnicke> But if I were you, I'd also test against the base edition and service provider edition when they release shortly
21:20:54 <regXboi> can we release the hounds?
21:21:06 <Konstantin_> thx
21:21:34 <edwarnicke> regXboi: Lets pause to talk about the hounds for a moment first
21:21:51 <edwarnicke> First, the procedure
21:21:56 <edwarnicke> I think we probably want to do:
21:22:02 <edwarnicke> 1)  Run your change versions job
21:22:20 <edwarnicke> 2)  Check for manual issues and ammend the patch from change versions
21:22:26 <edwarnicke> 3)  Merge the version change patch
21:22:37 <edwarnicke> 4)  Run your dry run with IGNORE_SNAPSHOTS=false
21:22:42 <edwarnicke> 5)  Run you release
21:22:47 <edwarnicke> As a special caveat
21:22:51 <edwarnicke> If you depend on someone else
21:22:53 <edwarnicke> Wait for them
21:23:04 <edwarnicke> I think the only case of that we have is openflowplugin depending on openflowjava
21:23:15 <edwarnicke> But you guys would know better than I
21:23:20 <regXboi> that all looked sane
21:23:24 <edwarnicke> Does anyone else have anything to add to that?
21:23:42 <edwarnicke> Its easier if we get this right the first time ;)
21:23:48 <hideyuki> edwarnicke: thank you.
21:24:43 <hideyuki> VTN Project will submit a patch soon.
21:24:49 <edwarnicke> hideyuki: You can thank me when the integration builds pass testing :)
21:25:11 <edwarnicke> OK... lets get this done folks so integration can do its thing and we can run the tests and know we are all good to go :)
21:25:11 * rovarga gave up hope on the versions job
21:25:13 <Madhu> edwarnicke: i just recovered from crash .
21:25:28 <suchiraman> Just in case could you post the new version of the controller we must use. yangtools change had to be placed manually even though change version job ran correcty.
21:25:29 <Madhu> lost all the messages that u had typed except the last few steps
21:25:41 <edwarnicke> rovarga: For me at least, the version job does a good job as far as it goes.. it just doesn't catch everything given our current pom file structure
21:25:45 <Madhu> mind unicasting the steps ? edwarnicke  ?
21:25:49 <colindixon> suchiraman: the controller has about 87 versions
21:25:53 <edwarnicke> Madhu: Whats the last thing you have?
21:26:04 <Madhu> 4)  Run your dry run with IGNORE_SNAPSHOTS=false [16:22:37
21:26:19 <rovarga> edwarnicke: yeah ... it didn't do anything for us, but then it's trivial for us to bump versions :)
21:26:21 <edwarnicke> 5)  Run your release
21:26:32 <edwarnicke> Madhu: #5 was the end
21:26:45 <Madhu> edwarnicke: sorry :) i need before #4
21:26:48 <rovarga> #info bgpcep bump to controller released artifacts is https://jenkins.opendaylight.org/bgpcep/job/bgpcep-verify/1388/
21:26:54 <Madhu> i have the tail from #4 onwards
21:26:56 <edwarnicke> #topic Everybody else release
21:27:05 * regXboi concerned
21:27:07 <edwarnicke> Could we get a #info from folks working the five step plan to release
21:27:12 <edwarnicke> So we know everyone is engaged?
21:27:22 <regXboi> #info opendove is on version changes
21:27:23 <edwarnicke> Your name, project, and that you are working on it
21:27:38 <edwarnicke> (or better yet, what regXboi just did, #info-ing the point of progress ;) )
21:28:22 <regXboi> edwarnicke... what's the current version of sal in the cut artifact?
21:28:26 <goldavberg> #info lispflowmapping is on version changes
21:28:35 <colindixon> First, the procedure
21:28:35 <colindixon> I think we probably want to do:
21:28:37 <colindixon> 1)  Run your change versions job
21:28:38 <colindixon> 2)  Check for manual issues and ammend the patch from change versions
21:28:40 <colindixon> 3)  Merge the version change patch
21:28:41 <colindixon> 4)  Run your dry run with IGNORE_SNAPSHOTS=false
21:28:42 <colindixon> 5)  Run you release
21:28:43 <colindixon> As a special caveat, if you depend on someone else, wait for them. I think the only case of that we have is openflowplugin depending on openflowjava, but you guys would know better than I
21:30:21 <hideyuki> #info VTN Project submitted a patch for the version change: https://git.opendaylight.org/gerrit/#/c/4934/
21:33:11 <Madhu> edwarnicke: the controller-bulk-release job
21:33:13 <Madhu> sorry
21:33:17 <Madhu> bulk-release-2 job
21:33:22 <regXboi> opendove isn't picking up dependency changes
21:33:24 <Madhu> is that the one u created recently ?
21:33:40 <Madhu> i originally copied the job that GiovanniMeo got for the bulkrelease
21:35:33 <edwarnicke> Ah
21:35:34 <edwarnicke> Wait
21:35:38 <edwarnicke> Let me check on the merge job
21:36:17 <edwarnicke> regXboi: What artifacts aren't you seeing (we have the ones I've spot checked in nexus)
21:36:44 <regXboi> clustering.services
21:37:08 <Konstantin_> On controller start : !MESSAGE Bundle reference:file:../lib/logging.bridge-0.4.1-SNAPSHOT@1:start not found.
21:37:11 <regXboi> networkconfig.neutron
21:37:26 <edwarnicke> clustering services is here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/controller/clustering.services/0.5.0/
21:37:50 <edwarnicke> networkconfig.neutron is here: v
21:37:51 <edwarnicke> https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/controller/networkconfig.neutron/0.4.1/
21:38:05 <regXboi> ok
21:38:09 <regXboi> I can find the rest
21:38:11 <regXboi> :)
21:38:26 <regXboi> so opendove is up to date and I'm just confused
21:40:04 <edwarnicke> Konstantin_: What is the output of
21:40:09 <edwarnicke> ss | grep bridge
21:40:13 <edwarnicke> At the OSGI console ?
21:40:14 <cdub> odd
21:40:40 <cdub> not seeing distibution.opendaylight:0.1.1
21:40:53 <Konstantin_> From run.sh -start
21:41:32 <hideyuki> regXboi: Are you working on creating a patch for opendove for the version change?
21:41:47 <regXboi> no, there is no patch
21:41:53 <regXboi> I'm getting ready to move to #2
21:42:30 <hideyuki> regXboi: ok. so will you manually create a patch?
21:42:52 <colindixon> hideyuki: I think regXboi is saying that he thinks opendove is up-to-date on versions
21:42:53 <regXboi> no, I'm saying that I'm checking the version #s right now
21:43:15 <colindixon> edwarnicke, cdub: what's going on with not seeing distribution.opendaylight:0.1.1?
21:43:42 <cdub> perhaps it's not in nexus?
21:43:46 <edwarnicke> colindixon: Its here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/controller/distribution.opendaylight/0.1.1/
21:43:54 <edwarnicke> Guys, one thought that just occurred to me
21:44:00 <cdub> hmm, weird, i keep getting an error
21:44:01 <edwarnicke> The release repo is different from the snapshot repo
21:44:04 <edwarnicke> If you do not have both
21:44:09 <edwarnicke> You wont' find the release artifacts
21:44:23 <edwarnicke> The release repo is: https://nexus.opendaylight.org/content/repositories/opendaylight.release/
21:44:30 <edwarnicke> Its possible some of you only have the snapshot repo
21:44:33 <edwarnicke> In your pom files
21:44:40 <suchiraman> Running version change job but not seeing the patch. Anyone else see this problem?
21:44:44 <suchiraman> https://jenkins.opendaylight.org/affinity/job/affinity-version-changes/lastBuild/console
21:44:52 <edwarnicke> Please make sure you have the release repo
21:44:55 <hideyuki> regXboi: i see.
21:45:01 <edwarnicke> because if you don;'t, version change won't find the release artifacts
21:45:30 <suchiraman> edwarnicke: please clarify what you mean by "use release repo".
21:45:41 <regXboi> ah now that might explain it
21:45:48 <edwarnicke> I'm hoping so :)
21:46:31 <regXboi> I hope your telling me you want release back in the poms
21:46:47 <regXboi> in the repository block
21:47:38 <edwarnicke> regXboi: In the repository block yes
21:47:50 <edwarnicke> And if you depend on yangtools, possibly in the pluginRepository block as well
21:48:00 <regXboi> I thought that's what you were going to say
21:49:00 <edwarnicke> (I don't think we have any plugins from projects that are not yangtools)
21:50:00 <edwarnicke> Quick advice, if you are looking for controller versions... you can look at https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/controller walk down to the one you are intereted in, and pick the latest version up ther
21:50:02 <edwarnicke> there
21:50:14 <regXboi> #info opendove rewinding back to before #1
21:52:52 <edwarnicke> regXboi: Anything you need help on?
21:52:58 <rovarga> #info bgpcep verified and merged into repository https://git.opendaylight.org/gerrit/#/c/4932/
21:53:27 <edwarnicke> rovarga: Could we get a link to your merge job?
21:53:33 <colindixon> edwarnicke: regXboi and I are just watching this go and hoping it doesn't break anything: https://jenkins.opendaylight.org/opendove/job/opendove-verify/139/console
21:54:02 <edwarnicke> suchiraman: Release artifacts are in this repo: https://nexus.opendaylight.org/content/repositories/opendaylight.release/
21:54:26 <regXboi> colindixon - brb
21:54:30 <edwarnicke> You need a <repository> for it in your <repositories> section, and also in your <pluginRepositories> section if you are using yangtools (which provides plugins)
21:54:39 <colindixon> suchiraman: this is a (hopefully correct) example of adding the release repos: https://git.opendaylight.org/gerrit/#/c/4939/
21:54:42 <rovarga> edwarnicke: it's queued up behind, as we needed a small fix in our regression tests
21:56:54 <rovarga> example of repositories/pluginRepositories is at https://git.opendaylight.org/gerrit/gitweb?p=bgpcep.git;a=blob;f=commons/parent/pom.xml;h=9562c15772446f85d6f14052d7ad86396f332d64;hb=HEAD
21:57:22 <regXboi> #info opendove getting the release repository information merged
21:58:27 <rovarga> #info bgpcep-on-released-versions merge job is at https://jenkins.opendaylight.org/bgpcep/job/bgpcep-merge/567/
21:59:34 <hideyuki> #info vtn-on-released-versions merge job is at https://jenkins.opendaylight.org/vtn/job/vtn-merge/182/
22:00:07 <goldavberg> #info lispflowmapping-on-released-versions merge job is at https://jenkins.opendaylight.org/lispflowmapping/job/lispflowmapping-merge/151/
22:00:14 <regXboi> #info opendove back to step #1
22:01:10 <regXboi> question on the versions
22:01:19 <hideyuki> regXboi: go ahead.
22:01:21 <regXboi> when we cut releases our own snapshots change?
22:01:42 <edwarnicke> regXboi: After your dryrun has been successful, you will run the release job
22:02:25 <regXboi> that's not quite what I meant
22:02:28 <regXboi> but that's ok
22:02:34 <edwarnicke> regXboi: Please clarify :)
22:02:48 <regXboi> so version change nicely picked up all the controller changes
22:02:58 <regXboi> of course all the internal references are still SNAPSHOT
22:03:14 <regXboi> and frankly, that won't change, because this is development
22:03:23 <edwarnicke> regXboi: Its normal for your internal dependencies to be at SNAPSHOT until you run the release job
22:03:28 <suchiraman> Where can I find a version change job to copy from? My version change job is  not picking up changes.
22:03:49 <suchiraman> And, do I need both prepare-only and dry-run (atm I only have prepare-only).
22:04:00 <colindixon> suchiraman: did you add the release nexus repos
22:04:09 <edwarnicke> suchiraman: prepare-only is dry run
22:04:14 <suchiraman> colindixon: already have it in the pom.xml
22:04:29 <suchiraman> hence that doesn't seem to be the problem in affinity case.
22:04:49 <suchiraman> Top-level pom.xml has it, should I check all pom.xml?
22:06:27 <suchiraman> https://git.opendaylight.org/gerrit/gitweb?p=affinity.git;a=blob;f=pom.xml;h=72ac5f5f7decc1cb46bcb9fa863fbf86bce0867f;hb=HEAD
22:07:05 <edwarnicke> suchiraman: Your repos look correct at at glance
22:07:26 <suchiraman> Not clear why version-change comes back empty. This error mean anything?
22:07:28 <edwarnicke> suchiraman: https://jenkins.opendaylight.org/controller/job/controller-version-changes/
22:07:47 <LuisGomez> edwarnicke: i run the versions change for integration and so far only detects changes in lisp and of java but no controller changes, is this ok?
22:07:49 <edwarnicke> suchiraman: Can you send the link to your Jenkins Job run /
22:07:52 <Madhu> edwarnicke: what is ur recommendation for the step #5
22:07:57 <suchiraman> https://jenkins.opendaylight.org/affinity/job/affinity-version-changes/lastBuild/console
22:08:07 <Madhu> shud we copy the existing prepare-only
22:08:08 <edwarnicke> LuisGomez: Do you have the release repo in your pom files?
22:08:10 <Madhu> and make it push ?
22:08:11 <rovarga> #info bgpcep merge check done, running pre-release dryrun at https://jenkins.opendaylight.org/bgpcep/job/bgpcep-bulk-release-prepare-only/7/
22:08:24 <edwarnicke> Madhu: Controllers is https://jenkins.opendaylight.org/controller/job/controller-bulk-release-prepare-only-2/
22:08:33 <Madhu> edwarnicke: is that a new one ?
22:08:44 <Madhu> i copied Giovanni's one before
22:08:49 <Madhu> what is the difference ?
22:08:50 <edwarnicke> I think I did it mid to late last week
22:09:06 <edwarnicke> To incorporate hideyuki's brilliant IGNORE_SNAPSHOTS sollution :)
22:10:09 <Konstantin_> #info Defense4all 1.0.7 is Ok with this controller version
22:10:14 <regXboi> #info opendove now merging in updated controller definitions
22:12:51 <LuisGomez> edwarnicke: not sure what the release repo means, i have not touched the pom files since you prepared them...
22:14:34 <rovarga> #info bgpcep pre-release checking complete
22:15:06 <Madhu> anyone have ideas on : Can't release project due to non released dependencies :org.opendaylight.ovsdb:commons.ovsdb:pom:1.0.0-SNAPSHOT for the prepare-only ?
22:15:11 <Madhu> the is an internal dependency
22:15:30 <Madhu> i thought the internal dependency will be SNAPSHOT until the actual release is performed.
22:16:47 <cdub> Madhu: is that what you are doing now?
22:17:06 <Madhu> cdub: yes. am on prepare-only phase
22:17:10 <rovarga> #info bgpcep release build running at https://jenkins.opendaylight.org/bgpcep/job/bgpcep-bulk-release/1/
22:17:22 <Madhu> versions caught all the external dependencies (controller and yang tools)
22:17:51 <Madhu> hideyuki: do u have any insights ?
22:18:02 <Madhu> i see that VTN also follows the same commons approach.
22:19:43 <regXboi> #info opendove now doing dry-run without IGNORE-SNAPSHOTS
22:19:48 <rovarga> Madhu: could that trailing slash in relativePath be the problem?
22:20:06 <hideyuki> I think this merge is wrong https://git.opendaylight.org/gerrit/#/c/4942/1
22:20:09 <rovarga> (just checking)
22:20:36 <Madhu> rovarga: no idea :)
22:20:39 <Madhu> i can check
22:20:44 <hideyuki> Madhu: no idea.
22:21:15 <regXboi> #info opendove just hit Madhu's issue
22:21:29 <rovarga> in the two releases internal deps such as this were just fine
22:21:29 <Madhu> rovarga: u mean : ../commons/parent/
22:21:36 <rovarga> Madhu: yes
22:21:37 <Madhu> make it ../commons/parent
22:21:48 <Madhu> lemme try that.
22:22:08 <cdub> hideyuki: you mean it should have gone to s/-SNAPSHOT// instead of bumping version and going to next -SNAPSHOT?
22:23:14 <hideyuki> I thought that first we generate release artifacts for the three version, and after that move to new SNAPSHOT version.
22:23:47 <cdub> yes, appears to have skipped over release
22:23:54 <hideyuki> cdub: yes, this is what i mean.
22:24:40 <cdub> LuisGomez: ping...^^^
22:26:51 <hideyuki> edwarnicke: Madhu How do you think about this patch: https://git.opendaylight.org/gerrit/#/c/4942/
22:27:27 <Madhu> hideyuki: that is strange
22:27:29 <hideyuki> I'm not sure on this. so i would like more opinions.
22:27:29 <LuisGomez> cdub: hi
22:27:32 <michal_rehak> hideyuki: openflowjava is not released yet
22:27:55 <edwarnicke> michal_rehak: is oflibMichal working on it :)
22:28:02 <ekarlso> release meeting still going ?
22:28:04 <michal_rehak> edwarnicke: yes
22:28:14 <edwarnicke> ekarlso: yes
22:28:19 <ekarlso> holy crap :p
22:28:23 <ekarlso> takes a long time ? :p
22:29:05 <hideyuki> michal_rehak: so you mean that the patch is correct?
22:29:32 <michal_rehak> for now there is nothing better I guess
22:29:38 <regXboi> Madhu, you figure out the SNAPSHOT problem?
22:29:53 <Madhu> regXboi: am trying rovarga suggestion of removing the trailing /
22:30:07 <regXboi> let me check mine, I don't think I have the trailing /
22:30:26 <rovarga> #info bgpcep release 0.3.0 complete, checking repo/nexus now
22:30:26 <cdub> michal_rehak: openflowjava cset 7613492f4 has 0.1 release in it
22:30:38 <regXboi> oh
22:30:43 <regXboi> I think I may know the problem
22:32:27 <regXboi> well... I don't have the trailing slash in the path and I hit the same issue
22:33:01 <Madhu> regXboi: what is that sir ?
22:33:03 <regXboi> might there be something relating to the parent pom being a SNAPSHOT?
22:33:40 <rovarga> #info bgpcep repo ready for 0.3.1 development, nexus artifacts are published
22:33:41 <regXboi> when I do some searching on the error message, it looks like the parent needs to be released first before the rest of the poms
22:33:45 <regXboi> but I'm not 100% sure
22:34:02 <colindixon> Madhu: we're seeing this: https://jenkins.opendaylight.org/opendove/job/opendove-bulk-release-dryrun/lastFailedBuild/
22:34:29 <edwarnicke> ekarlso: We had a little bit of a rocky start
22:34:47 <edwarnicke> OK... Madhu What is your issue?
22:34:58 <edwarnicke> And how many folks are seeing something similar?
22:35:19 <colindixon> edwarnicke: see the link I just put up
22:35:22 <Madhu> colindixon: edwarnicke am trying rovarga suggestion to remove the trailing /
22:35:33 <colindixon> same for regXboi and opendove
22:35:47 <suchiraman> offline for 30 mins
22:37:00 <Madhu> rovarga: that didn't help
22:37:07 <Madhu> edwarnicke: the problem is
22:37:22 <Madhu> ovsdb bundles depend on the internal SNAPSHOT versions of ovsdb.commons
22:37:31 <Madhu> prepare-only didn't like that
22:37:41 <hideyuki> #info VTN release build running at https://jenkins.opendaylight.org/vtn/job/vtn-bulk-release/1/
22:37:44 <Madhu> https://jenkins.opendaylight.org/ovsdb/job/ovsdb-bulk-release-prepare-only/8/console
22:37:46 <edwarnicke> Madhu: link to your prepare-only?
22:38:00 <edwarnicke> (I spent all weekend fighting things like this in controller... I may be good at it by now :) )
22:38:47 <regXboi> oh
22:38:52 <regXboi> heh
22:38:54 <regXboi> hehehehehehe
22:39:15 <Madhu> edwarnicke:  u got the link ?
22:39:15 <regXboi> has anybody looked at http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html
22:39:19 <Madhu> https://jenkins.opendaylight.org/ovsdb/job/ovsdb-bulk-release-prepare-only/8/console
22:39:23 <edwarnicke> Madhu: Try adding a module for your commons parent pom to your root pom.xml
22:39:36 <regXboi> that would do it
22:39:38 <Madhu> that we added already
22:39:38 <edwarnicke> What's happening is this
22:39:47 <edwarnicke> Gerrit?
22:39:48 <Madhu> Giovanni did
22:40:16 <rovarga> Madhu, edwarnicke: also, the top-level pom.xml lists commons as parent
22:40:29 <rovarga> that might be the problem
22:40:34 <Madhu> https://git.opendaylight.org/gerrit/#/c/4763/1/pom.xml
22:40:46 <edwarnicke> Because all I see in your root pom.xml is modules for ovsdb/, northbound/ovsdb, neutron, distribution/opendaylight
22:41:16 <Madhu> edwarnicke: okay. adding commons as a module
22:41:28 <Madhu> how is it going to help.
22:41:33 <Madhu> u were about to say that :)
22:41:42 <rovarga> because right now your commons is not being built
22:41:46 <edwarnicke> Madhu: Check your HEAD on master, I don't see that there
22:41:54 <Madhu> rovarga: yes.
22:42:03 <Madhu> but i manually changed commons
22:42:12 <Madhu> to take care of the SNAPSHOT issues that versions didn't catch
22:42:16 <edwarnicke> Madhu: I see your HEAD on Master at :
22:42:18 <Madhu> isn't that enough ?
22:42:18 <rovarga> release plugin does not pick up stuff which is not being built
22:42:19 <regXboi> trying the same thing on opendove, edwarnicke
22:42:20 <edwarnicke> https://www.irccloud.com/pastebin/X5UvKtJZ
22:42:34 <edwarnicke> https://www.irccloud.com/pastebin/0Q08nV1L
22:42:44 <edwarnicke> (and that's the pom.xml I see)
22:42:46 <rovarga> also, I think you need to remove that <parent> declaration from top-level pom.xml (only)
22:42:49 <edwarnicke> It doesn't build commons.ovsdb
22:42:58 <Madhu> rovarga: giovanni added that
22:43:05 <Madhu> https://git.opendaylight.org/gerrit/#/c/4763/1/pom.xml
22:43:13 <edwarnicke> OK guys
22:43:17 <Madhu> to solve the issue of Tags.
22:44:08 <Madhu> ok trying with module added
22:44:35 <rovarga> Madhu: sorry, I was mistaken
22:45:15 <Madhu> rovarga: so adding <module>will solve it ?
22:45:17 <edwarnicke> Quick tutorial on trying all of this locally if you are stuck:
22:45:19 <Madhu> am trying it anyways :)
22:45:20 <edwarnicke> https://www.irccloud.com/pastebin/wX1U2vIV
22:46:06 <rovarga> Madhu: yes, I am pretty sure that just adding a <module>commons/ovsdb</module> will solve it
22:46:25 <Madhu> ok. thanks rovarga edwarnicke
22:46:26 <rovarga> commons/parent I mean
22:47:42 <cdub> Madhu: it works if you run it from commons/parent
22:47:58 <edwarnicke> Madhu: And you can use the instructions I provided for trying it locally rather than roundtripping through Jenkins until you get it working
22:48:01 <edwarnicke> OK... who else is stuck?
22:48:11 <regXboi> I'm in the same place as Madhu was
22:48:17 <regXboi> but I'm trying your suggestion already
22:48:20 <regXboi> merging it in
22:48:32 <regXboi> and if it doesn't work then I'll look at local stuff
22:48:39 <regXboi> or pointing colindixon at it
22:48:47 <regXboi> as I need to walk away *very* soon :(
22:48:49 <colindixon> yeah
22:48:52 <colindixon> I'm looking
22:49:01 <colindixon> though I'm not a committer on opendove which may make things harder
22:49:06 <colindixon> but tykeal can kick stuff for me I guess
22:49:23 <tykeal> what am I kicking?
22:49:36 <regXboi> hopefully nothing
22:49:50 <tykeal> hope not, I'm trying to update an integration job ;)
22:49:52 <tykeal> :D
22:49:53 <regXboi> but I have to walk away soon
22:50:42 <edwarnicke> regXboi: Can you use my instructions for trying the build locally?
22:50:50 <regXboi> haven't tried
22:51:02 <edwarnicke> colindixon: You can try the instructions I provided up thread for building locally to try to debug
22:51:08 <colindixon> edwarnicke: I am
22:51:10 <regXboi> haha!
22:51:17 <regXboi> #info opendove passed dry run
22:51:30 * colindixon does a happy dance
22:51:40 <regXboi> your fix worked edwarnicke - put the parent in the release pom as a module
22:52:00 <edwarnicke> regXboi: Oh good :)
22:52:07 <regXboi> so, time to cut opendove?
22:52:09 <regXboi> or just a rug?
22:52:10 <edwarnicke> Madhu: How are you doing
22:52:11 <edwarnicke> regXboi:
22:52:16 <edwarnicke> First check a few things
22:52:20 <edwarnicke> First
22:52:21 <regXboi> like?
22:52:22 <edwarnicke> Run it locally
22:52:27 <edwarnicke> use
22:52:46 <Madhu> yep.
22:52:51 <edwarnicke> grep -r --include=pom.xml SNAPSHOT to see if you have any stray SNAPSHOT mentions in variables and things that didn't get updated
22:52:52 <Madhu> failed on git-push command
22:52:55 <Madhu> so am good to go i guess
22:53:14 <edwarnicke> Madhu: That's actually good news, because it means everything else worked and so you should be able to get the dry run job to work
22:53:15 <regXboi> run which locally?
22:53:30 <regXboi> the dry run?
22:53:34 <edwarnicke> Madhu: Please check for lingering SNAPSHOTs as indicated above with the grep
22:54:01 <edwarnicke> regXboi: https://www.irccloud.com/pastebin/wX1U2vIV (the equivalent of running dry run locally which means you can see locall the results)
22:54:09 <edwarnicke> (word of warning about doing the local build
22:54:10 <regXboi> got it
22:54:13 <edwarnicke> It does lots of stuff
22:54:16 <edwarnicke> Make sure to run
22:54:22 <edwarnicke> git hard --rest
22:54:24 <edwarnicke> and
22:54:27 <edwarnicke> git clean -f -x
22:54:37 <edwarnicke> before adding anything to commit upstream
22:54:45 <colindixon> git reset --hard
22:54:53 <Madhu> edwarnicke: why do we need grep -r --include=pom.xml SNAPSHOT ?
22:54:55 <regXboi> after running it?
22:54:58 <edwarnicke> (note these will blow away local changes that are not commited... so run them before *editing* anything locally)
22:55:05 <Madhu> the local bundles are in SNAPSHOT anyways
22:55:15 <Madhu> all the dependencies are clean of SNAPSHOT
22:55:17 <edwarnicke> regXboi: Make sure you have a clean git status before running it, use reset and clean after
22:55:47 <edwarnicke> Madhu: After locally running the prepare only it should have moved all your local bundles to being release versions
22:55:50 <edwarnicke> Thus the check
22:56:18 <regXboi> ok, the local run is blowing up
22:56:41 <edwarnicke> regXboi: blowing up how?
22:56:51 <regXboi> nevermind
22:56:55 <regXboi> I can't cut and paste anymore
22:57:40 <Madhu> edwarnicke: yes.
22:57:45 <Madhu> is working as expected
22:57:47 * regXboi notes edwarnicke should be happy that I switched to linux two weeks ago or I'd be a REAL pita
22:57:51 <Madhu> so lemme push the module change
22:57:57 <Madhu> and let the jenkins job take over
22:58:27 <edwarnicke> Madhu: Did you check to make sure the prepare job updated all your snapshots locally to releases? (don't push those updates.. but want to make sure it worked)
22:59:08 <Madhu> yep
22:59:11 <Madhu> it did change
22:59:48 <edwarnicke> Madhu: Excellent :)
23:00:25 <regXboi> still haven't passed the local version
23:00:28 <regXboi> so ...
23:00:41 <edwarnicke> regXboi: What is the local version complaining about
23:01:18 <regXboi> it complained about files having been changed after a hard reset
23:01:26 <regXboi> and something else that I don't 100% remember
23:01:31 <edwarnicke> What is your git status ?
23:01:59 <regXboi> clean right now
23:02:11 <regXboi> but this is my third try :)
23:02:14 <regXboi> oh yeah
23:02:20 <edwarnicke> OK, and when you run the local prepare build, what does it complain about a the end precisely?
23:02:27 <regXboi> one time blew up because the command line wants integration test
23:02:30 <regXboi> and we don't have that
23:02:41 <edwarnicke> Ah
23:02:47 <edwarnicke> I presume that was a doable fix
23:02:48 <regXboi> so this is try #3
23:02:56 <regXboi> yeah I think I can figure that one out :)
23:03:22 <regXboi> but aren't you glad I'm not doing this in windows :)
23:03:56 <regXboi> so I got to where it wanted me to provide a key to push up to git
23:04:08 <Madhu> #info ovsdb prepare-only is successful
23:04:13 <colindixon> regXboi: perfect
23:04:14 <Madhu> onto the bulk-release
23:04:20 <colindixon> that means were good to go
23:04:36 <regXboi> grep is empty
23:04:55 <edwarnicke> regXboi: That's exactly the right place to fail :)
23:05:03 <regXboi> and the grep is empty
23:05:03 <edwarnicke> You *won't* be able to push to git
23:05:09 <edwarnicke> But its done everything else by then
23:05:16 <edwarnicke> And if your grep for SNAPSHOTS is empty
23:05:20 <edwarnicke> You are good to go :)
23:05:20 <regXboi> it was
23:05:28 <regXboi> #info opendove pulling the trigger
23:05:34 <edwarnicke> Madhu: Congratulations!
23:05:50 <Madhu> am copying the bulk-release-2 from controller project now
23:06:00 <Madhu> (i had the bulk-releaes copied before)
23:06:13 <regXboi> #info watching paint dry: https://jenkins.opendaylight.org/opendove/job/opendove-bulk-release/1/
23:07:59 <regXboi> oops
23:08:02 <edwarnicke> ?
23:08:03 <regXboi> well that didn't work
23:08:31 <regXboi> https://jenkins.opendaylight.org/opendove/job/opendove-bulk-release/1/console
23:08:34 <colindixon> INFO] [WARNING] The requested profile "integrationtests" could not be activated because it does not exist.
23:08:35 <colindixon> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project parent: Failed to deploy artifacts/metadata: No connector available to access repository opendaylight-release (${nexusdeploy}/repositories/opendaylight.release/) of type default using the available factories WagonRepositoryConnectorFactory -> [Help 1]
23:08:37 <regXboi> I've got the wrong repository
23:08:44 <regXboi> that's embarrassing
23:08:54 <colindixon> aj
23:09:10 <edwarnicke> tykeal: Looks like maybe the opendove Jenkins permissions aren't set up correctly
23:09:18 <tykeal> ?
23:09:24 <regXboi> ed
23:09:27 <edwarnicke> regXboi: That looks like the repo you want to deploy to... releases...
23:09:28 <regXboi> should that be opendove.release?
23:09:32 <edwarnicke> No
23:09:34 <regXboi> not opendaylight.release?
23:09:37 <regXboi> oh
23:09:41 <edwarnicke> Everybody goes into opendaylight.release
23:09:42 <regXboi> well then, n/m
23:10:09 <regXboi> question is what can I do to help fix it?
23:10:13 <rovarga> hmm.. do you have $nexusdeploy defined? ;)
23:10:16 <regXboi> or is it now out of my hands?
23:10:29 <edwarnicke> I think its something we have to work with tykeal on
23:11:02 <regXboi> well...
23:11:12 <regXboi> rovarga may be correct
23:11:37 <regXboi> I need to change that pom
23:11:50 <rovarga> we usually have ${nexusproxy} instead :)
23:12:03 <edwarnicke> tykeal: can you help regXboi with repo permissions? His Jenkins doesn't seem to have permission to deploy to the release repo
23:12:10 <regXboi> I have nexusproxy elsewhere
23:12:13 <regXboi> edwarnicke
23:12:18 <regXboi> it's not a tykeal problem at this point
23:12:22 <tykeal> his repo has the permissions, I just checked them
23:12:29 <tykeal> [INFO] [WARNING] The requested profile "integrationtests" could not be activated because it does not exist.
23:12:33 <regXboi> rovarga pointed out the problem
23:12:48 <regXboi> I have a mistake in my parent pom
23:13:03 <regXboi> so... how to fix?
23:13:10 <rovarga> tykeal: that should be okay, it's copy&paste from controller, which has such a profile. regXboi does not, I guess
23:13:19 <edwarnicke> tykeal: That's just a warning
23:13:28 <regXboi> hello folks?
23:13:29 <edwarnicke> And regXboi can fix it by removing the profile flag in the Jenkins Job
23:13:55 <hideyuki> Is someone working on cutting artifacts for openflow java now?
23:14:02 <regXboi> the problem is there is a mistake in the parent pom
23:14:03 <rovarga> regXboi: fix the pom... check the repo for changes
23:14:15 <regXboi> I did
23:14:22 <rovarga> I guess it should be in pre-release state
23:14:25 <colindixon> regXboi: I'm looking
23:14:45 <regXboi> no it isn't
23:14:50 <rovarga> hmm
23:14:50 <regXboi> the POM is in release state
23:14:52 <tykeal> hideyuki: oflibMichal is trying to get openflowjava to release but the job keeps failing in a weird way that I'm uncertain how to resolve
23:15:18 <hideyuki> tykeal: i see. thank you.
23:16:24 <regXboi> so, the question is how do I back this out?
23:16:38 <colindixon> regXboi: are you doing things or should I try to push a fix
23:16:51 <colindixon> if it's just adding the nexusdeploy to be defined in the parent pom I can do that
23:17:00 <regXboi> or change it to nexusproxy
23:17:08 <colindixon> which one should we do?
23:17:09 <colindixon> edwarnicke:
23:17:10 <regXboi> I used nexusproxy elsewhere but forgot
23:17:46 <colindixon> ok
23:17:51 <regXboi> I already have pushed
23:18:09 <regXboi> what I'm worried about is everything is not SNAPSHOT now
23:18:17 <regXboi> so what will that do to the release job?
23:18:32 <colindixon> that's a good question
23:18:38 <Madhu> #info ovsdb https://jenkins.opendaylight.org/ovsdb/job/ovsdb-bulk-release-2/1/ done folks
23:18:47 <Madhu> edwarnicke: is that all ?
23:18:54 <regXboi> no, Madhu, you can help me :)
23:19:15 <Madhu> regXboi: sure once am given the green light :)
23:19:18 <edwarnicke> Madhu: Please check in nexus for the release versions of your artifacts to make sure they are there
23:19:26 <Madhu> i do see https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/ovsdb/
23:19:44 <edwarnicke> Madhu: Please also pull master for ovsdb and check to make sure you moved to the next SNAPSHOT for your local artifacts in your pom files
23:19:51 <edwarnicke> Madhu: Excellent news
23:19:52 <Madhu> yep.
23:19:58 <edwarnicke> Would you be so kind as to lend a hand to others?
23:21:16 <michal_rehak> tykeal: regarding openflowjava failure
23:21:28 <rovarga> regXboi: so opendove master does not seem to carry the effects of a release job
23:21:39 <regXboi> ok
23:21:40 <michal_rehak> tykeal: I googled up this error message and there was a problem with post actions
23:21:44 <regXboi> that's good news
23:21:46 <rovarga> can you point me at the job which fialed?
23:21:52 <michal_rehak> tykeal: successful build do not have post-actions
23:21:59 <colindixon> rovarga: https://jenkins.opendaylight.org/opendove/job/opendove-bulk-release/1/console
23:22:01 <tykeal> ?
23:22:25 <regXboi> no worries
23:22:29 <michal_rehak> tykeal: could sending emails after build cause failure?
23:22:30 <regXboi> I think I can just rerun it
23:22:39 <tykeal> michal_rehak: no
23:22:46 <michal_rehak> tykeal: ok
23:22:58 <colindixon> rovarga, regXboi: merge, then re-run?
23:23:12 <regXboi> yes on merge
23:23:16 <hideyuki> #info VTN Hydrogen release complete, checking repo/nexus now
23:23:38 <tykeal> michal_rehak: the failure is due to maven getting back a 400 Bad Request error from nexus during the upload phase. The strange thing is that it seems to be completing when we look at what ends up in nexus
23:23:47 <rovarga> regXboi: so looking at the releasejob
23:23:56 <Madhu> #info OVSDB is done. nexus looks good and next SNAPSHOT is active in master
23:24:10 <rovarga> you have branch name set to $BRANCH-doingrelease-$JOB_NAME-$BUILD_NUMBER, it should be only $BRANCH
23:24:24 <regXboi> um, I copied that from elsewhere
23:24:28 <colindixon> oh
23:24:38 <rovarga> which is why there are no changes to the repo :)
23:24:38 <colindixon> there's a release-2 job I think
23:24:57 <colindixon> which can be copied from controller
23:25:01 <colindixon> Madhu just did that
23:25:13 <regXboi> so I'm completely confused now
23:25:28 <colindixon> https://jenkins.opendaylight.org/controller/job/controller-bulk-release-2/
23:25:34 <Madhu> yes colindixon
23:25:39 <Madhu> i just copied them to ovsdb
23:25:43 <Madhu> and thats it.
23:25:53 <regXboi> oh
23:26:00 <regXboi> I thought that is what I copied
23:26:26 <regXboi> ok, but once I merge I can try and re-run the bulk-release?
23:26:34 <edwarnicke> FYI... openflowjava is hitting the same issue: https://jenkins.opendaylight.org/openflowjava/job/openflowjava-bulk-release/5/consoleFull
23:26:38 <rovarga> I htink you copied your -prepareonly job as per edwarnick's instructions, sans changing that branch
23:27:07 <regXboi> well... let's try pulling the trigger agin
23:27:09 <regXboi> er again
23:27:39 <colindixon> watches
23:29:32 <colindixon> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project parent: Failed to deploy artifacts/metadata: No connector available to access repository opendaylight-release (${nexusproxy}/repositories/opendaylight.release/) of type default using the available factories WagonRepositoryConnectorFactory -> [Help 1]
23:29:34 <edwarnicke> suchiraman: Are you around, what is your status?
23:29:35 <colindixon> https://jenkins.opendaylight.org/opendove/job/opendove-bulk-release/2/console
23:29:44 <regXboi> no love
23:29:47 <edwarnicke> colindixon: Could you google on that error and see what google knows?
23:29:55 <colindixon> trying
23:30:26 <regXboi> oh lordy
23:30:37 * regXboi begins to think he's a complete idiot
23:30:39 <rovarga> regXboi: your parent does not define nexusproxy
23:30:48 <regXboi> rovarga: +1
23:31:29 <colindixon> I think we're all punch drunk at this point
23:31:45 <rovarga> +  <properties>
23:31:46 <rovarga> +    <nexusproxy>http://nexus.opendaylight.org/content</nexusproxy>
23:31:49 <rovarga> +  </properties>
23:31:59 <regXboi> yeah I know
23:32:05 <regXboi> I define it everywhere else I use it
23:32:12 <regXboi> went looking
23:33:03 <tykeal> colindixon: I haven't been drinking any punch
23:33:09 <rovarga> I think we'll need to figure out/document project layout best practices
23:34:17 <edwarnicke> rovarga: Damn straight
23:34:43 * edwarnicke has been drinking all day... but Pellegrino sparkling water usually doesn't effect him much
23:34:43 <colindixon> regXboi: do you have this or want me to toss in a hand?
23:35:03 <regXboi> feel free to throw in a commit
23:35:29 <regXboi> my workspace just went wonkie
23:36:43 <colindixon> done
23:37:07 <regXboi> thanks
23:40:30 <colindixon> edwarnicke: suchiraman said she'd be out for 30 minutes a while back just so you nkow
23:40:31 <colindixon> know
23:43:15 <edwarnicke> colindixon: How long ago was that?
23:43:47 <colindixon> edwarnicke: not sure
23:44:21 <colindixon> past what I have buffered in IRC :-/
23:44:26 <colindixon> somebody else have logs back that far?
23:44:36 * regXboi looks for help from st. vidicon
23:46:02 * colindixon dances
23:46:05 * regXboi dances in the street
23:46:12 <colindixon> opendove release job succeeded
23:46:13 <regXboi> #info opendove is released
23:46:25 <regXboi> ok folks - I should have been out the door 15 minutes ago
23:46:37 <colindixon> things appear to be here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/opendove/
23:46:38 <regXboi> colindixon - check the repo - I'll check master
23:46:47 <colindixon> what else do I need to do edwarnicke ?
23:47:26 <regXboi> I checked master
23:47:34 <regXboi> we're done AFAIK
23:47:37 <regXboi> and all - I'm out!
23:47:42 <regXboi> find you tomorrow
23:47:53 <colindixon> thanks for the extra work regXboi
23:48:01 <regXboi> rovarga: thanks - I owe you a beer if you are in SJ next week
23:48:24 <edwarnicke> Quick check, we have releases for bgpcep, controller, defense4all, ovsdb, vtn, yangtools.  We need to finish affinity,opendove, openflowjava, openflowplugin,  lispflowmapping, snmp4sdn... and then integration... is that correct?
23:48:45 <edwarnicke> OK.. move opendove to the done column :)
23:48:47 <colindixon> edwarnicke: I believe opendove just finished
23:48:57 <regXboi> the controller stuff did
23:49:06 <regXboi> the rpm stuff for the virt edition is still up in the air
23:49:08 <rovarga> regXboi: I think we'll have one or two cold ones :)
23:49:10 <regXboi> so put it inbetween
23:49:13 <edwarnicke> suchiraman: Where are we on affinity?
23:49:21 <regXboi> bye all!
23:49:36 <edwarnicke> suchiraman: Where are we on affinity ?
23:49:50 <edwarnicke> oflibMichal: Where are we on openflowjava
23:50:00 <edwarnicke> michal_rehak: I presume you are waiting on openflowjava ?
23:50:12 <edwarnicke> Christine_: Where are we on snmp4sdn ?
23:50:13 <oflibMichal> edwarnicke: rovarga is helping now
23:50:16 <michal_rehak> edwarnicke: true
23:50:21 <edwarnicke> rovarga: Thank you so much! :)
00:00:29 <suchiraman> back online now
00:00:43 <edwarnicke> suchiraman: Where are you?  How can I help? :)
00:02:46 <suchiraman> version change job still not picking up changes. Job looks the same as the one on other repos. So not sure how to catch version changes.
00:03:24 <suchiraman> Error is here: https://jenkins.opendaylight.org/affinity/job/affinity-version-changes/lastBuild/console
00:06:32 <suchiraman> Strange, re-running picked up changes correctly.
00:07:05 <edwarnicke> Guys...be cautious
00:07:11 <edwarnicke> If you took your changes job from controller
00:07:16 <edwarnicke> It has -DallowSnapshots=true
00:07:19 <edwarnicke> For doign your release
00:07:22 <edwarnicke> You want -DallowSnapshots=false
00:09:46 <edwarnicke> suchiraman: Let me look at your changes job
00:10:03 <suchiraman> Weird --- it just started working.
00:10:26 <suchiraman> edwarnicke: It's here and worked this time. https://jenkins.opendaylight.org/affinity/job/affinity-version-changes/lastBuild/
00:10:54 <suchiraman> (Setting allowsnapshots correctly now)
00:13:12 <edwarnicke> suchiraman: OK... I spotted something as starting point
00:13:57 <edwarnicke> Under "Source Code Management" -> "Branches to Build" -> "Advanced" click "Wipe out workspace before build"
00:14:52 <edwarnicke> suchiraman: See if that helps
00:15:00 <edwarnicke> Its a way you differ from the jobs that are working
00:15:06 <oflibMichal> #info openflowjava successfully released
00:15:32 <suchiraman> I just fixed that. Independently the job passed (after waiting for an hour or so), not sure if there is a purge job running somewhere that took care of this.
00:15:33 <edwarnicke> oflibMichal: Congratulations!
00:15:38 <edwarnicke> oflibMichal: What is the link
00:15:38 <edwarnicke> ?
00:15:59 <edwarnicke> suchiraman: Are you getting a Gerrit for changes?
00:16:18 <oflibMichal> edwarnicke: https://jenkins.opendaylight.org/openflowjava/job/openflowjava-bulk-release/6/
00:16:18 <suchiraman> yes, getting the patches in for affinity version changes.
00:19:00 <oflibMichal> thanks all participants for their time and help
00:19:04 <edwarnicke> suchiraman: Yay!
00:19:14 <edwarnicke> Make sure that the changes are release versions not snapshots
00:19:38 <hideyuki> suchiraman: i see SNAPSHOT version for jersey in analytics/northbound/pom.xml.
00:19:43 <hideyuki> suchiraman: is it OK?
00:19:57 <suchiraman> Hmm.I'm checking.
00:20:24 <hideyuki> suchiraman: note: I checkouted from this patch https://git.opendaylight.org/gerrit/#/c/4958/
00:20:30 <michal_rehak> #info openflowplugin dependencies versions updated to releases git.opendaylight.org/gerrit/4960
00:21:15 <suchiraman> So, for external snapshot I assume I should manually remove the snapshot tag. Correct?
00:21:33 <edwarnicke> Yes
00:21:41 <michal_rehak> suchiraman: we use external snapshots?
00:21:56 <michal_rehak> external to project or external to ODL
00:21:58 <michal_rehak> ?
00:22:10 <hideyuki> suchiraman:  i see  <hosttracker.version>0.5.1-SNAPSHOT</hosttracker.version> in pom.xml
00:23:51 <edwarnicke> hideyuki: Thank you for helping :)
00:23:56 <suchiraman> virgo, commons.logback, jersey-servlet.
00:24:01 <suchiraman> What should I use for these/
00:25:02 <hideyuki> suchiraman: i think that jersey is a framework for REST API.
00:26:17 <cdub> suchiraman: do you have an oustanding review in gerrit?
00:26:54 <hideyuki> suchiraman: virgo is related to OSGi, and common.logback is related to logggin. so i think you need these modules.
00:28:29 <edwarnicke> suchiraman: Check and see what controller is using
00:28:30 <suchiraman> Latest hostrracker is 0.5.1?
00:28:39 <suchiraman> checking controller deps
00:28:51 <edwarnicke> It would seem so: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/controller/hosttracker/
00:29:01 <edwarnicke> At least at release (non SNAPSHOT)
00:31:20 <hideyuki> suchiraman: yes, i think 0.5.1 of hosttracker is fine.
00:34:47 <michal_rehak> #info openflowplugin - started openflowplugin-bulk-release-prepare-only jenkins job
00:41:07 <goldavberg> #info lispflowmapping finished deployment :)
00:41:15 <edwarnicke> suchiraman: How is it going?
00:41:41 <suchiraman> Just pushed some more -snapshot changes.
00:41:57 <suchiraman> Verify/merge running.
00:42:02 <suchiraman> Next up is prepare-only.
00:43:09 <edwarnicke> Did you check with
00:43:23 <edwarnicke> grep -r --include=pom.xml SNAPSHOT .
00:43:31 <edwarnicke> To make sure you only have project internal snapshots?
00:45:07 <michal_rehak> #info openflowplugin - started openflowplugin-bulk-release jenkins job
00:45:46 <michal_rehak> edwarnicke: I use mvn dependency:tree -nsu | grep 'SNAPSHOT'
00:46:05 <edwarnicke> michal_rehak: That's probably smarter than what I was doing with grep :)
00:46:40 <cdub> grep is nice and fast ;)
00:46:44 <hideyuki> suchiraman: did you delete 0.5.8-SNAPSHOT for maven-sal-api-gen-plugin  in affinity/yang/pom.xml?
00:46:54 <michal_rehak> edwarnicke:  well.. I usually use less or redirection to file, because tree could be time consuming
00:47:20 <cdub> also i don't think mvn dependency:tree -nsu will show you plugins
00:47:23 <cdub> for example
00:47:48 <cdub> affinity has 0.5.8-SNAPSHOT ... what hideyuki said ;)
00:48:01 <suchiraman> removing 0.5.8-snapshot.
00:48:23 <hideyuki> cdub: suchiraman ok.
00:48:30 <suchiraman> It is in pom's that are not used.So mvn dependency tree comes back clean. Still, I'll commit a small change.
00:49:23 <hideyuki> suchiraman: i see. sorry for disturbing you.
00:49:56 <suchiraman> np. prepare-only success.
00:51:21 <edwarnicke> suchiraman: Link ?
00:51:28 <suchiraman> https://jenkins.opendaylight.org/affinity/job/affinity-bulk-release/lastBuild/console
00:52:28 <edwarnicke> suchiraman: Perhaps I'm misreading... but that job looks like it failed, not success... did I misunderstand?
00:53:13 <hideyuki> this one? https://jenkins.opendaylight.org/affinity/job/affinity-bulk-release-prepare-only/4/
00:53:36 <edwarnicke> awesome... that looks good :)
00:53:44 <michal_rehak> #info openflowplugin release = 0.0.2
00:53:48 <edwarnicke> suchiraman: Due to some issues with lingering SNAPSHOTS at times
00:53:53 <michal_rehak> good night
00:53:59 <suchiraman> Two more snapshots. Now gone.
00:54:02 <cdub> suchiraman: i don't see anything pending in gerrit, so is everything merged?
00:54:03 <oflibMichal> good night
00:54:18 <suchiraman> Yes all merged.
00:54:24 <suchiraman> prepare only again.
00:54:25 <edwarnicke> I've been suggesting to folks that they do a local prepare build so they can check for lingering snapshots as decribed here: https://www.irccloud.com/pastebin/wX1U2vIV
00:54:37 <edwarnicke> And then check with
00:54:59 <edwarnicke> grep -r --include=pom.xml SNAPSHOT .
00:55:05 <cdub> suchiraman: ok, current is looking clean to me
00:55:15 <edwarnicke> To make sure that there are no remaining SNAPSHOTS after doign the local prepare
00:55:18 <edwarnicke> Its paranoid
00:55:23 <edwarnicke> But useful
00:55:30 <edwarnicke> cdub: Thank you for checking :)
00:57:05 * rovarga is off. see you tomorrow/next week :)
01:03:48 <hideyuki> thank you all. bye.
01:04:08 <cdub> hideyuki: thanks for the marathon work you've done!
01:04:15 <cdub> hideyuki: rest well ;)
01:05:01 <tykeal> ok.. I'm going to step away from the terminal for a little bit. If folks need me, just give a ping. I should get a page
01:05:25 <edwarnicke> suchiraman: How is it going?
01:05:51 <cdub> tykeal: you shouldn't tell us that
01:05:59 <tykeal> shouldn't tell you what?
01:06:00 <cdub> we'll start paging you all the time! ;)
01:06:03 <tykeal> that I get pages?
01:06:05 <tykeal> lol
01:06:31 <tykeal> you start paging me all the time I just add you to the filter to not page me ;)
01:06:46 <tykeal> almost like giving you a plonk... but not quite :D
01:06:46 <cdub> heh, fair 'nuff
01:08:03 <suchiraman> scrubbing pom.xml -- should be done soon.
01:09:45 <edwarnicke> :)
01:19:45 <suchiraman> edwarnicke: https://jenkins.opendaylight.org/affinity/job/affinity-bulk-release/lastBuild/console (error string is about ref HEAD not a symbolic ref)
01:20:58 <suchiraman> edwarnicke: no idea why but checkin in last step is failing.
01:21:24 <edwarnicke> Let me look
01:22:15 <edwarnicke> Looking at your job
01:22:41 <edwarnicke> OK... I think I see the issue
01:23:03 <edwarnicke> Set Source Code Management -> Git -> Branches to build -> Advanced -> Checkout/merge to local branch (optional) to $BRANCH
01:23:11 <edwarnicke> In your bulk-release job
01:27:08 <suchiraman> edwarnicke: looks like the release job worked. Could you please confirm.
01:27:17 <suchiraman> https://jenkins.opendaylight.org/affinity/job/affinity-bulk-release/
01:27:50 <edwarnicke> Your binary artifacts are present
01:27:57 <edwarnicke> Let me check your source
01:28:53 <edwarnicke> Source looks good :)
01:28:55 <edwarnicke> Congratulations
01:29:12 <suchiraman> thanks all!
01:29:27 * colindixon does a dance
01:29:42 <suchiraman> yay!
01:41:58 <colindixon> so, we're waiting on SNMP4SDN and Integration
01:42:01 <colindixon> ?
01:42:16 <cdub> colindixon: afaik, yes
01:42:28 <cdub> colindixon: edwarnicke sent email to SNMP4SDN
01:42:58 <cdub> i'll tyr to work with them this evening (/ their morning)
01:44:19 <colindixon> sounds good
01:44:26 <colindixon> I'll be around in case I can help
01:44:40 <cdub> cool
02:57:05 <cdub> Christine_: good morning!
02:57:13 <Christine_> hi!
02:57:51 <cdub> Christine_: i looked through snmp4sdn tree, looks like an attempt and then rollback of sync w/ controller and release
02:57:54 <Christine_> sorry I just left
02:58:05 <cdub> Christine_: no problem, was pretty late for you
03:00:39 <Christine_> cdub: will the steps to finishing cutting be complicated? the other team member paiwei will be here later, then we can start
03:01:05 <cdub> Christine_: shouldn't be too complicated
03:01:34 <cdub> Christine_: i have to help get my kids into bed, so just ping me when paiwei is here
03:01:53 <Christine_> sure thanks
03:35:42 <edwarnicke> #endmeeeting
03:35:45 <edwarnicke> #endmeeting