J3 Issue ? ? ? ?
avatar rdeutz
rdeutz
10 Aug 2018

Current situation

We have a lot tools and scripts doing this and that. Most of the time only a few people know what this scripts are and if they are needed at all. Furthermore we have the new situation that a clone from the repository isn't installable.

How to solve the tooling jungle

We already have robo.li (https://robo.li/) and using it for some tasks. I have started to move some of the Testing Task into Robo (https://github.com/joomla-projects/robo-joomla). It comes with a lot of build in tasks for making releases. It would be great if we could make tasks for package a release and steps around making a release. This will be needed for the PR testing platform and will also help the release leads.

Next steps

  1. We need to now what tools and scripts we are using.
  2. Move and document scripts

Goal

One tool to rule them all (might not 100% possible because of node, but we can have a robo task to call npm)

avatar rdeutz rdeutz - open - 10 Aug 2018
avatar joomla-cms-bot joomla-cms-bot - change - 10 Aug 2018
Labels Added: ? ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 10 Aug 2018
avatar joomla-cms-bot joomla-cms-bot - labeled - 10 Aug 2018
avatar franz-wohlkoenig franz-wohlkoenig - change - 11 Aug 2018
Status New Discussion
avatar franz-wohlkoenig franz-wohlkoenig - change - 11 Aug 2018
Category Repository Unit Tests
avatar brianteeman
brianteeman - comment - 15 Aug 2018

Not really sure what you are expecting anyone to say here.

avatar mbabker
mbabker - comment - 15 Aug 2018

If you want to use it for new things, go ahead. We already have working tools and scripts for other tasks, unless refactoring them is going to be more maintainable under Robo I don't see the benefit in yet another change for the sake of change.

avatar HLeithner
HLeithner - comment - 15 Aug 2018

I rewrote my component packaging today from phing to robo and its so much simpler now ;)

If you need help just say what todo because i have no overview.

avatar rdeutz
rdeutz - comment - 15 Aug 2018

@brianteeman request for comments doesn't mean you have to comment

@mbabker the goal is to have more people able to use and to maintain our tooling, I have better things to do as change something that doesn't need a change

@HLeithner for a start https://github.com/joomla-projects/robo-joomla/projects

avatar brianteeman
brianteeman - comment - 19 Aug 2018

@rdeutz I kow understand why you posted th8is here - I had thought it would be better to have been in a productin chat

avatar franz-wohlkoenig franz-wohlkoenig - change - 5 Apr 2019
Labels Added: J3 Issue
avatar franz-wohlkoenig franz-wohlkoenig - labeled - 5 Apr 2019
avatar franz-wohlkoenig franz-wohlkoenig - change - 7 Apr 2019
Labels Added: ?
avatar franz-wohlkoenig franz-wohlkoenig - labeled - 7 Apr 2019
avatar brianteeman
brianteeman - comment - 21 May 2019

Is this still an "under discussion" item?

avatar HLeithner
HLeithner - comment - 21 May 2019

Yes it is and in testing hannes is already doing some work.

Edit: Wrong ticket, yes it still a topic

avatar brianteeman
brianteeman - comment - 21 May 2019

Sorry I obviously wasn't clear - Is this still under discussion and needs to remain open

avatar HLeithner
HLeithner - comment - 21 May 2019

Yeah I don't think so by lack of interest

avatar HLeithner HLeithner - change - 21 May 2019
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2019-05-21 08:55:30
Closed_By HLeithner
Labels Added: ?
Removed: ?
avatar HLeithner HLeithner - close - 21 May 2019
avatar joomla-cms-bot joomla-cms-bot - change - 21 May 2019
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 21 May 2019

Add a Comment

Login with GitHub to post a comment