Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next Nightly build #595

Closed
donalej opened this issue Oct 30, 2015 · 14 comments
Closed

Next Nightly build #595

donalej opened this issue Oct 30, 2015 · 14 comments

Comments

@donalej
Copy link

donalej commented Oct 30, 2015

Hello,

I would like to know when will the next nightly build for Win64?

Thanks

@frankmorgner
Copy link
Member

there are build artifacts available here https://ci.appveyor.com/project/LudovicRousseau/opensc

@frankmorgner
Copy link
Member

we will only provide official binaries for releases

@CardContact
Copy link
Member

I've updated the wiki frontpage with the link to appveyor.

What about the old nightly builds on sourceforge ? Do we remove them ?

Do we still need references to versions before 0.14 ?

Is it correct, that we don't have nightly tarballs anymore (Can be created with github anyway) ?

@CardContact CardContact reopened this Jan 7, 2016
@vletoux
Copy link
Contributor

vletoux commented Jan 15, 2016

The Appveyor link https://ci.appveyor.com/project/LudovicRousseau/opensc/ is inaccurate because it includes also PR.
The correct link is: https://ci.appveyor.com/project/LudovicRousseau/opensc/branch/master

@frankmorgner
Copy link
Member

@viktorTarasov how do you proceed with your jenkins? If I understood correctly you are not so tightly involved anymore, so I assume it is better to remove the integration with your boxes (i.e. stop upload of nightlies, stop building with github hook, remove the references from the wiki)!?

@CardContact links to the old releases and their binaries should stay where they are. The new home is github, so any new release should be done here. @viktorTarasov or @LudovicRousseau , could you please activate the automatic import of github releases for SourceForge (this way SourceForge essentially only acts as a mirror without our manual interference)?

@CardContact
Copy link
Member

Fine with me.

Do we know who maintains packages for the various distributions ?

We've received feedback that certain Ubuntu builds are done without OpenSSL, so some of the features are disabled.

@LudovicRousseau
Copy link
Member

@frankmorgner I added a web-hook in the github project as documented in https://sourceforge.net/p/forge/documentation/GitHub%20Importer/#releases

The next OpenSC github release should be automatically available on https://sourceforge.net/projects/opensc/files/ but I don't know in what subdirectory the release will be present. We will see.

@viktorTarasov
Copy link
Member

@frankmorgner
agree to remove from wiki the references to the non-public services

I will stop the upload of the nightly builts and
propose to remove the 'nightly' folder from sourceforge.

@frankmorgner
Copy link
Member

@LudovicRousseau you can see the result of a different project here http://sourceforge.net/projects/vsmartcard/files/. On 2015-12-27 I imported existing releases to sourceforge and created the webhook. On 2016-01-05 I created a new release which got imported via the webhook.

@frankmorgner
Copy link
Member

I agree with @viktorTarasov

@viktorTarasov
Copy link
Member

propose to remove the 'nightly' folder from sourceforge.

as well as folders with the not-majors releases

@frankmorgner
Copy link
Member

@viktorTarasov what's the current status, do you need any help?

@viktorTarasov
Copy link
Member

  • no more GitHub webhook to opensc.fr/jenkins;
  • Files on sourceforge contain only released tarball and windows binaries.

@frankmorgner
Copy link
Member

@viktorTarasov by the way, for the next release we should use the draft a release feature of github. This allows collecting all binaries (windows, mac, autoconf source) before publishing everything. This will allow sourceforge to import everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants