•  
      request #9582 Version changes in the marketplace/tuleap update site are not reflected in the "Install more connectors" view from Tasks Repositories (Mylyn)
    Infos
    #9582
    Patrick-Jeffrey Pollo Guilbert (epatpol)
    2016-10-26 10:20
    2016-10-13 18:03
    9861
    Details
    Version changes in the marketplace/tuleap update site are not reflected in the "Install more connectors" view from Tasks Repositories (Mylyn)
    As seen in bug #9532, installing the Tuleap Connector by using the Mylyn wizard made for installing other connectors still installs an old 2.2 build from 2014. I don't know how it works and where it fetches those versions, so I asked on the mylyn-dev mailing list.

    The version from the marketplace (and thus the one on the update site hosted on tuleap.net) and the one in that wizard should always be the same, to avoid any further confusion.
    Mylyn
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Empty
    References
    References list is empty

    Follow-ups

    User avatar

    I messed the Jenkinsfile config, sorry about that. I managed to build 'master' and push it to update site.

    It should work for stable as well, I let you test.

    User avatar
    @vaceletm I tried running the job by pushing to either stable or update and it failed with what seems to be an error in the plugin? Or I misconfigured the only few options I had?

    Just to confirm that the repo can be built, I've built the update site locally and it seems to work correctly.

    Thank you!
    User avatar

    @epatpol I updated the job so it takes 2 parameters:

    • GIT_BRANCH (default to master): name of the branch or tag that should be built
    • MYLYN_REPOSITORY (either 'update' or 'stable'): the mylyn repo where the content should be pushed.

    Please let me know if it works as expected.

    User avatar

    So, as a first step, I propose to have a job to update "stable" update site and if there is a need to flag/tag repositories, we will create them later on.

    User avatar
    My bad, I completely forgot that the marketplace update site is hosted at the same place as this one! In this case yes we wouldn't have to push a patch to Mylyn but simply update this one. So I guess the same kind of job would be great too.

    As for the stable-X.Y.Z I'm not sure, as I don't know how they planned to release the connector a few years back. I guess maybe it's for archiving old versions? Let's say we update stable with 2.3, we would also create stable-2.3 just in case 2.4 becomes stable in the future, but I'm not sure. As of right now I don't think people can install using those old stable versions using the marketplace or the mylyn view, so it's probably only used to store old artifacts.
    User avatar

    We sure can update  http://eclipse.tuleap.net/mylyn.tasks/stable it's pretty much the same thing that what we have done for  http://eclipse.tuleap.net/mylyn.tasks/update your are already using.

    If we setup the same kind of job for stable, is that OK for you or do we need something else ?

    (I've seen in the update site that there are stable-X.Y.Z, is that needed ?)

    User avatar

    Hi @vaceletm, thanks for asking but I don't know how you guys can help, but after investigating a bit, maybe you know something about another update site where the plugin is being hosted right now.

    I asked a question on the mylyn-dev mailing list and got an answer hereBy looking at the patch somebody made a while ago, I can see that every connector is described in that xml with a siteUrl attribute i.e siteUrl="http://eclipse.tuleap.net/mylyn.tasks/stable". Maybe you guys know who maintains this update site? This is where the 2014 build is being hosted right now.

    If we can't push the new build to http://eclipse.tuleap.net/mylyn.tasks/stable, I think it would be better to simply submit a patch to change that attribute to the tuleap.net update site instead, maintaining the feature/plugin at one place seems like the more logical choice. From what I can see in the plugin.xml, other connectors also have url hosted with different domains (not all eclipse.org) so that shouldn't be an issue.

    Patrick