OpenDevStack/Lobby

Richard Attermeyer

@rattermeyer

Hi, just released a new version of generator-node-express-typscript on npm. This version is synced with the upstream project.

Michael Sauter

@michaelsauter

@rattermeyer Thanks!

Michael Sauter

@michaelsauter

@rattermeyer Actually, looking at the new code, I cannot find index.ts anymore - is that intended? I think it was an addition by opitz

Michael Sauter

@michaelsauter

@tjaeschke I just noticed that the Nexus credentials are spread around in the shared library etc - did you guys remove them already?

Torsten Jaeschke

@tjaeschke

@michaelsauter In the shared library not yet, but in the quickstarters. I will remove it. Currently I'mn working to get the restructured code running after a merge mess up with an older head.

Michael Sauter

@michaelsauter

okay

thanks for removing, I was working a bit on it today to fix those things properly but it is a bit of a rabbithole :)

Torsten Jaeschke

@tjaeschke

GettingStarted.md

Even if I'm not finished yet, would you please take a look, if the Getting Strated is complete. The repo URLs are missing. I will add them as soon as the repos are there.

Richard Attermeyer

@rattermeyer

@michaelsauter I will have a look

Richard Attermeyer

@rattermeyer

that was unitentional. was marked as removed by upstream. will add it again.

Michael Sauter

@michaelsauter

I’m going to read through the getting started today

Richard Attermeyer

@rattermeyer

I've protected the master / production branches on the repos requiring at least 1 review.

All contributors: Please enable 2FA for github.

gerardcl

@gerardcl

done! thanks

Clemens Utschig

@clemensutschig

@/all - wäre there notes from the last jf call?

Michael Sauter

@michaelsauter

@clemensutschig yes, in the JF room

Clemens Utschig

@clemensutschig

I dont See that room...

Michael Sauter

@michaelsauter

Ah! I added you now. Gitter is weird ...

Clemens Utschig

@clemensutschig

anyone up to help with provision app ...

there is some serious fuckup .. (that I helped one or the other way I guess).

call to createProject on bitbucket works

and createRepo afterwards fails with a 401

something is really really fucked

Clemens Utschig

@clemensutschig

good lord - I finally found this .. the provision app is one big beast ... I am almost back in the game

Clemens Utschig

@clemensutschig

@all

any chance that we completely automate the testing for ODS ...

we have found a hell lot of small issues over the last weeks,... that automation would have caught ... seriously - maybe we can have a student on this ...?!

just asking

Michael Sauter

@michaelsauter

@/all what do you think about having another pre-1.0 release for ODS? I think it would be good to have another “stable” release that ideally another non-BI user can use so that we can gather feedback and improve things before we go 1.0. I think it is easier to make bigger changes without this big “1.0” tag on it :) plus the last weeks/months have shown there is a lot of nitty-gritty things that are still a bit brittle

Clemens Utschig

@clemensutschig

Sure... i am ok with this to shoot for 0.8 or Alike for end of oct.

Für now

For now we really need help

There is just soo many Open ties. i am fixibg what i find...

Clemens Utschig

@clemensutschig

@/all - prov App is broken- does Not create webhooks.. the API changed with 5.13 upgrade.. i have a fix for this tmrw night

Scala quickstarter Borken as well ..

Michael Sauter

@michaelsauter

from a SemVer standpoint I would say next release is 0.2 … those numbers are not like floating points, so e.g. after a 0.9 the next release can be 0.10 … I guess to avoid the confusion they could have chosen another separator, e.g. 0-2 :)

Torsten Jaeschke

@tjaeschke

Agree. Next version should be 0.2. Even if we do releases in short intervals

Borja Minyana

@borja44

hi there

gerardcl

@gerardcl

hola!

Richard Attermeyer

@rattermeyer

Hi there, any idea why there is some discrepancies in the create-projects.sh script. the secrets template is processed for -dev and -test, but not for -cd projects. Would exepct either to not process it at all and create a seperate cd_user for every initiative or process it for all three. @michaelsauter : any ideas?

Richard Attermeyer

@rattermeyer

there is only the token secret available. how do you handle it from the process on your side. do you manually set up the cd_user secret for every new project?

Clemens Utschig

@clemensutschig

@rattermeyer - cd-jenkins-master

objects:

apiVersion: v1
data:
password: '${CD_USER_PWD}'
username: '${CD_USER_ID}'
kind: Secret
metadata:
name: cd-user-with-password
labels:
```
template: cd-jenkins-master
```
type: kubernetes.io/basic-auth

Richard Attermeyer

@rattermeyer

hmm. right. but it was not created inside the project. had to create it by hand. need to check what happened there.

Clemens Utschig

@clemensutschig

@rattermeyer - super weird ..

can you check rundeck and see whats there

you re-installed/Uploaded the templates - rightß

Where communities thrive

People

Repo info

Activity