These are chat archives for fiji/fiji

8th
Sep 2016
Curtis Rueden
@ctrueden
Sep 08 2016 01:21
@kephale @tinevez We still don't have Jenkins job for depositing ClearVolume artifacts onto maven.imagej.net. I would love to set those up though.
Jean-Yves Tinevez
@tinevez
Sep 08 2016 11:39
Ok. After the issue fiji/TrackMate#87 , I felt like I should invest time to make a new 3D viewer for TrackMate.
As yours activities go forth, I will be able to.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 11:39
@tinevez: are you gonna be at the december hackathon?
Jean-Yves Tinevez
@tinevez
Sep 08 2016 11:40
Most likely yes.
Very likely.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 11:40
very good!
Jean-Yves Tinevez
@tinevez
Sep 08 2016 11:40
I still hope to move forward with
TrackMate 3D viewer before ;)
Ulrik Günther
@skalarproduktraum
Sep 08 2016 11:41
@ctrueden: i’d love to have that, for scenery as well. please let me know what you need from my side, i’m more than happy to support this :)
so @kephale and me are working on a scenery-based 3d viewer replacement, i think it’d be great if we could bundle our efforts
@tinevez: if i understand fiji/TrackMate#87 correctly, it’s about exporting TrackMate’s tracks to the fiji 3D viewer? or TrackMate’s own?
Jean-Yves Tinevez
@tinevez
Sep 08 2016 11:44
No, I think Richard means that you could display TrackMate results in the 3D viewer (as spheres and lines) for 3D visualization over time.
But now you can't because of the issues with the Fiji 3D Viewer. I thought I would skip this bullet but no.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 11:47
it’d probably be quite easy to change your backend to scenery, also circumventing fiji’s 3d viewer … i could give you a walkthrough if you like
Jean-Yves Tinevez
@tinevez
Sep 08 2016 11:48
Well so far I have been stuck at adding ThreeDViewer and friends as a dependency for TrackMate ...
Ulrik Günther
@skalarproduktraum
Sep 08 2016 11:48
okay, what’s the issue?
tpietzsch
@tpietzsch
Sep 08 2016 11:48
there are no artifacts...
Ulrik Günther
@skalarproduktraum
Sep 08 2016 11:48
oh
right
tpietzsch
@tpietzsch
Sep 08 2016 11:48
@skalarproduktraum @ctrueden it would be great if you could make this happen!
:+1:
Ulrik Günther
@skalarproduktraum
Sep 08 2016 11:49
sorry, i tend to forget about this :(
@ctrueden: okay, so jobs for clearvolume, cleargl, scenery and threedviewer… let me know what you need :)
(they all should have travis jobs already, if it helps we could also upload from there to maven.imagej.net)
Curtis Rueden
@ctrueden
Sep 08 2016 12:31
I have zero time right now. Could one of the other Jenkins admins please take care of it?
odinsbane
@odinsbane
Sep 08 2016 12:36
Is there a good way to crop/duplicate really large virtual stacks?
tpietzsch
@tpietzsch
Sep 08 2016 12:36
@ctrueden @skalarproduktraum if the projects are build by maven, I can set them up in the Jenkins Release-Version script
beyond that (gradle, travis, ...) I have no experience and wouldn't be of much help
Ulrik Günther
@skalarproduktraum
Sep 08 2016 12:38
@tpietzsch clearvolume is using gradle at the moment, but cleargl, scenery and threedviewer have poms
apparently you can also deploy directly from travis to a maven repo: https://coderwall.com/p/9b_lfq/deploying-maven-artifacts-from-travis
so if you could get me an account i could also take care of it, at least for everything in the clearvolume organisation
Curtis Rueden
@ctrueden
Sep 08 2016 13:20
@skalarproduktraum Interesting... do you understand the purpose of the travis branch?
Ulrik Günther
@skalarproduktraum
Sep 08 2016 13:22
@ctrueden as far as i get it they use the branch for storing travis settings, which is not really required
Curtis Rueden
@ctrueden
Sep 08 2016 13:30
OK, I get it now.
I don't get why people think that is a crazy usage of Travis, apart from the crazy usage of the travis branch.
You can just make a /.m2/settings.xml on master, and then it's clear which version of the settings was used to deploy each commit.
And you don't need the git clone craziness.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 13:31
yip
are the credentials for uploading to maven.imagej.net generated by jenkins?
(because i’m intrested doing it right from travis, and @tpietzsch was so kind to get me a jenkins account :+1: )
Curtis Rueden
@ctrueden
Sep 08 2016 13:38
Jenkins has its own user in the Nexus. I will make one for Travis, too.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 13:40
great! thank you!
Curtis Rueden
@ctrueden
Sep 08 2016 13:50
@skalarproduktraum I sent you credentials for maven.imagej.net personal account, as well as the new Travis account.
Curtis Rueden
@ctrueden
Sep 08 2016 16:07
@StephanPreibisch I fixed the failing Descriptor_based_registration build (needed to be updated to use Java 8 instead of Java 7). And I manually deployed your 2.1.0 commit. HTH.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 17:47
@ctrueden @tpietzsch @tinevez: the snapshot builds for scenery and cleargl 2 are now available at http://maven.imagej.net/content/repositories/snapshots/net/clearvolume/ and get updated with every successful travis ci build
Curtis Rueden
@ctrueden
Sep 08 2016 17:50
@skalarproduktraum Thanks!!
Eventually, we will still need release versions to be deployed, for stability. But for dev, I think this is a big step forward.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 17:50
thanks to you curtis, wouldn’t have been possible without your guidance :+1:
definitely, i’ll automate that in the future if a commit has a release tag
Curtis Rueden
@ctrueden
Sep 08 2016 17:51
Ha. Working with you is great Ulrik, because you just do things, and then they are done. It's refreshing. :wink:

i’ll automate that in the future if a commit has a release tag

Interesting. I hadn't thought of doing things that way. It doesn't solve the issue of needing to tweak the POM for 100% correctness though...

Ulrik Günther
@skalarproduktraum
Sep 08 2016 17:52
in gradle, that’s pretty easy — you can set the version to the git tag
and gradle autogenerates a pom before uploading
Curtis Rueden
@ctrueden
Sep 08 2016 17:52
Not sure how familiar you are with the SciJava dev lifecycle but basically, we have two different ways of doing releases, and one of them is proper but needs some tooling, and the other one just requires pushing to master but results in not-quite-correct releases.
ctrueden @ctrueden nods
Ulrik Günther
@skalarproduktraum
Sep 08 2016 17:53
it’s probably not possible in maven to do the same, is it?
Curtis Rueden
@ctrueden
Sep 08 2016 17:53
To set the version to the git tag?
Ulrik Günther
@skalarproduktraum
Sep 08 2016 17:54
yes
Curtis Rueden
@ctrueden
Sep 08 2016 17:54
Actually, it might be!
Ulrik Günther
@skalarproduktraum
Sep 08 2016 17:54
Curtis Rueden
@ctrueden
Sep 08 2016 17:54
more like: set the git tag in the <scm> section to match the current commit...
But it might be too dirty.
So, setting the version to a property is considered extremely dangerous in Maven land.
However, that is actually not what worries me. It's just the <scm><tag> section of the POM I'm talking about above.
Ulrik Günther
@skalarproduktraum
Sep 08 2016 17:55
maybe it’s the same in gradle land and nobody has told me :D
on a related note, would you mind if i add the gradle info to http://imagej.net/Travis and amend the info regarding maven by moving the upload task from the script section to the after_success section (which is better suited)?
Curtis Rueden
@ctrueden
Sep 08 2016 17:55
There are various chicken-and-egg problems, essentially, when it comes to making the version a property.
For the Travis page: you want to have a nice way of documenting how to do things with Gradle, without displacing the Maven-specific info? You could use tabs.
Here is an example of tabs.
As for shuffling stuff around, I leave that page entirely in your hands. :-)
Ulrik Günther
@skalarproduktraum
Sep 08 2016 18:08
okay, updated: http://imagej.net/Travis
Curtis Rueden
@ctrueden
Sep 08 2016 18:30
Thanks @skalarproduktraum! Looks nice.