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

doc: remove all hard coded version numbers to simplify release #2786

Merged
merged 1 commit into from
Dec 4, 2018

Conversation

monperrus
Copy link
Collaborator

baby pr for #2779

@@ -18,9 +18,16 @@ include: [_includes]
# variables

sidebar_tagline: Spoon
sidebar_version: version 7.0.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just for info, can't you define sidebar_version according to spoon_release?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that is another option, but I prefer to simply get rid of sidebar_version

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok


# this is replaced at deployment time by job https://ci.inria.fr/sos/job/Website Deployer/
# LATESTVERSION=`curl -s "http://search.maven.org/solrsearch/select?q=g:%22fr.inria.gforge.spoon%22+AND+a:%22spoon-core%22" | jq .response.docs[0].latestVersion`
# sed -i -e "s/^spoon_release: .*/spoon_release: $LATESTVERSION/" _config.yml
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this command pushed somewhere?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, in the Jenkins config, which is mirrored here https://github.com/SpoonLabs/spoon-ci-config

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know!

@tdurieux
Copy link
Collaborator

@GerardPaligot did before a script that automatically updates those version. I feel it is a better solution

@monperrus
Copy link
Collaborator Author

You're right, the problem is that this script is a bash monster that hasn't been executed and maintained for more than 4 years.

@tdurieux
Copy link
Collaborator

I just looked a the script (that is not really a monster), it seems that it is pretty simple to maintain and only minor changes are required.
see:
https://github.com/INRIA/spoon/blob/master/doc/_release/deploy_production.sh

@monperrus
Copy link
Collaborator Author

Thanks for the link.

Regardless of the script, I'm in favor of the simplification of this PR, on the ground that simpler means less error-prone today and in the future.

@GerardPaligot
Copy link
Contributor

That could be interesting to migrate all these old scripts from bash to a better and more maintainable language. You always use Maven to package your project, that could be interesting to migration to Gradle and create better scripts in Groovy or Kotlin for all these tasks that could be automatic. :)

@monperrus
Copy link
Collaborator Author

+100 for @GerardPaligot's comment. (good to see you Gérard :-)

For the next release, I'm considering writing some Python scripts.

@monperrus
Copy link
Collaborator Author

With no other comments, ready for merge.

@monperrus monperrus changed the title doc: remove all hard coded version numbers so as to prepare continuous delivery doc: remove all hard coded version numbers to simplify release Dec 1, 2018
@monperrus
Copy link
Collaborator Author

ready for merge

@surli surli merged commit 9219db0 into INRIA:master Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants