On 2/21/2022 5:36 PM, P.O. Jonsson wrote:
Does anyone remember what this setting is for in the build step for
the documentation?
:-- list change sets
curl %BUILD_URL%api/json
With Jenkins upgraded from http:// to https:// this seems to generate
an error
jenkins@DELLGX760 C:\Users\jenkins\workspace\ooRexx-docs-build>curl
https://build.oorexx.org/job/ooRexx-docs-build/102/api/json
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:--
--:--:-- 0
100 625 100 625 0 0 7052 0 --:--:-- --:--:--
--:--:-- 7183
<html><head><meta http-equiv='refresh'
content='1;url=/login?from=%2Fjob%2FooRexx-docs-build%2F102%2Fapi%2Fjson'/><script>window.location.replace('/login?from=%2Fjob%2FooRexx-docs-build%2F102%2Fapi%2Fjson');</script></head><body
style='background-color:white; color:white;'>
Authentication required
<!--
-->
</body></html>
As a second question: I am also looking for a volunteer (nudge, nudge
Gil) to migrate the documentation build jobs from the physical Windows
10 machine (intended for retirement) into a VM. I have a Windows 7 PRO
VM with a legit license I no longer use myself available for this
task. I take it it does not matter if we build on W7 or W10?
During or after this migration it would be great if we could make the
documentation build only when there are actual changes to the
documentation. My rather blunt setup of Gils build tools build
everything every time there is a commit which is mostly not related to
the documentation. I am more than happy to replace that with something
smarter. I will provide the necessary access information to whoever
wants to have a go at migrating the documentation jobs.
While I am unable to take on this task, I do have some thoughts on
making the process "smarter". In order to only build the documents that
have been changed, we need to know what level the previously-built
document is and what level the source in SVN is. I would suggest
creating a properties file whose entries are the document names with
values that are the revision level of each document. Then one could get
the current revision level of the source for the document and if it is
different than the value in the properties file for that document, we
need to rebuild the document AND update the properties file. I'm
attaching a short program that shows how to use the 'svn log' command to
get the current revision of a document.
@René: of course you were right, BUILD_URL is a setting within Jenkins
itself. I owe you a beer next time you are in Berlin :-)
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
/* Get the SVN revision level of a document. Expects one argument - the name of
the document specified as the directory name of the source under docs/trunk.
E.g. the Rexx Reference book is rexxref. */
parse arg doc
-- use the svn log command to get the most recent change info for the
document
svncmd = "svn log https://svn.code.sf.net/p/oorexx/code-0/docs/trunk/"doc
"-l 1"
address path svncmd with output stem log.
-- the second line of the output starts with the revision number; e.g.
r12347
parse var log.2 rev .
say "The" doc "document is at revision" rev"."
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
