Re: RFC: URLs for docs and released bits from CI
> > I submitted a revision today which makes some slight modification to
> > how the doit.py script is building docs, rpms and tarballs.
> >
> > https://phab.qadevel.cloud.fedoraproject.org/D1012
> >
> > My intention is to get this deployed to a non-staging setup soon but I
> > wanted to reach out to see if anyone had an issue for the URLs that
> > would end up being used.
> >
> > https://baseurl/docs/
> >
> > This path would contain docs for built per branch for
> > non-master branches and per-release-version when triggered on the
> > master branch. The 'latest' symlink will always be updated to point at
> > the most recent build on the master branch
> >
> >
> > https://baseurl/releases/
> >
> > Pretty much the same thing as for docs but with the rpms, srpms and
> > tarball(s) created during the CI build.
> >
> > Does this seem sane to everyone? Any comments/questions/suggestions? I'd
> > like to get the auto-docs functionality deployed soon - hopefully right
> > after F25 beta freeze is over.
> >
>
> Just wondering if URLs would looked better like this:
>
> https://{docs,releases}.baseurl/
>
> (assuming there's no technical issues with that).
I like the original proposal. Just visit https://baseurl/docs/ and you see the
project listing automagically through apache.
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: RFC: URLs for docs and released bits from CI
My reply ended up going only to Martin instead of to the list so I'm
re-sending.
On Fri, 23 Sep 2016 07:04:37 -0400 (EDT)
Martin Krizek wrote:
> - Original Message -
> > From: "Tim Flink"
> > To: qa-devel@lists.fedoraproject.org
> > Sent: Friday, September 23, 2016 12:09:56 AM
> > Subject: RFC: URLs for docs and released bits from CI
> >
> > I submitted a revision today which makes some slight modification to
> > how the doit.py script is building docs, rpms and tarballs.
> >
> > https://phab.qadevel.cloud.fedoraproject.org/D1012
> >
> > My intention is to get this deployed to a non-staging setup soon
> > but I wanted to reach out to see if anyone had an issue for the
> > URLs that would end up being used.
> >
> > https://baseurl/docs/
> >
> > This path would contain docs for built per branch for
> > non-master branches and per-release-version when triggered on the
> > master branch. The 'latest' symlink will always be updated to point
> > at the most recent build on the master branch
> >
> >
> > https://baseurl/releases/
> >
> > Pretty much the same thing as for docs but with the rpms, srpms and
> > tarball(s) created during the CI build.
> >
> > Does this seem sane to everyone? Any
> > comments/questions/suggestions? I'd like to get the auto-docs
> > functionality deployed soon - hopefully right after F25 beta freeze
> > is over.
> >
>
> Just wondering if URLs would looked better like this:
>
> https://{docs,releases}.baseurl/
>
> (assuming there's no technical issues with that).
The only potential issue there is that we only have so many "slots" for
subdomains in the SSL cert. I'm pretty sure we have 5 total so that
shouldn't be an issue, though.
I'm fine with either format. It shouldn't be too hard to switch over to
virtualhosts.
> Other thought I have is to have a index page at https://docs.baseurl/
> which would contain links to various project's version of docs. But
> I am hesitant as to how worth is it to spend time on it, so having
> apache default file listing might be good enough.
That's a good idea. Not sure how much work it'd take to get something
like that but it's at least worth looking in to.
> Either way, the proposed URLs and directory structure look sane to me.
Cool, thanks for looking it over.
Tim
> Thanks,
> Martin
> ___
> qa-devel mailing list -- qa-devel@lists.fedoraproject.org
> To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
pgpn1Y9OI2XYA.pgp
Description: OpenPGP digital signature
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: RFC: URLs for docs and released bits from CI
- Original Message -
> From: "Tim Flink"
> To: qa-devel@lists.fedoraproject.org
> Sent: Friday, September 23, 2016 12:09:56 AM
> Subject: RFC: URLs for docs and released bits from CI
>
> I submitted a revision today which makes some slight modification to
> how the doit.py script is building docs, rpms and tarballs.
>
> https://phab.qadevel.cloud.fedoraproject.org/D1012
>
> My intention is to get this deployed to a non-staging setup soon but I
> wanted to reach out to see if anyone had an issue for the URLs that
> would end up being used.
>
> https://baseurl/docs/
>
> This path would contain docs for built per branch for
> non-master branches and per-release-version when triggered on the
> master branch. The 'latest' symlink will always be updated to point at
> the most recent build on the master branch
>
>
> https://baseurl/releases/
>
> Pretty much the same thing as for docs but with the rpms, srpms and
> tarball(s) created during the CI build.
>
> Does this seem sane to everyone? Any comments/questions/suggestions? I'd
> like to get the auto-docs functionality deployed soon - hopefully right
> after F25 beta freeze is over.
>
Just wondering if URLs would looked better like this:
https://{docs,releases}.baseurl/
(assuming there's no technical issues with that).
Other thought I have is to have a index page at https://docs.baseurl/
which would contain links to various project's version of docs. But
I am hesitant as to how worth is it to spend time on it, so having
apache default file listing might be good enough.
Either way, the proposed URLs and directory structure look sane to me.
Thanks,
Martin
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
RFC: URLs for docs and released bits from CI
I submitted a revision today which makes some slight modification to how the doit.py script is building docs, rpms and tarballs. https://phab.qadevel.cloud.fedoraproject.org/D1012 My intention is to get this deployed to a non-staging setup soon but I wanted to reach out to see if anyone had an issue for the URLs that would end up being used. https://baseurl/docs/ This path would contain docs for built per branch for non-master branches and per-release-version when triggered on the master branch. The 'latest' symlink will always be updated to point at the most recent build on the master branch https://baseurl/releases/ Pretty much the same thing as for docs but with the rpms, srpms and tarball(s) created during the CI build. Does this seem sane to everyone? Any comments/questions/suggestions? I'd like to get the auto-docs functionality deployed soon - hopefully right after F25 beta freeze is over. Tim pgpfHNtiAeCOS.pgp Description: OpenPGP digital signature ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
