init not working as expected with pre-build

[jmcelreavey]

Bug description

I currently have the following logic in place:

tasks:
  - before: |
      printf "\n[settings]\napi_key = $WAKA_TIME_API_KEY\n" > ~/.wakatime.cfg
    prebuild: |
      docker-compose up -d
      yarn install
      yarn run database:migrate
    command: |
      docker-compose down
      docker network prune -f
      yarn run dev

This works perfectly, however, the documentation is telling me prebuild has been deprecated and I should replace it with init however when I do this it doesn't rebuild the init step, it runs during startup.

Steps to reproduce

Gitpod up the repository:
https://gitpod.io/#https://github.com/jmcelreavey/dev-job

Expected behavior

I would expect the GitHub pre-build functionality to see the init and run it prior to me starting the workspace

Example repository

https://github.com/jmcelreavey/dev-job

Anything else?

No response

[csweichel]

/schedule

[faisal-m16]

Same Issue. When creating a new workspace with extension no task is running.

tasks:
  - name: Run Client
    before: cd client
    init: yarn install
    command: yarn start
    env:
      DANGEROUSLY_DISABLE_HOST_CHECK: true
    openMode: tab-after
  - name: Run Server
    init: npm install
    command: npm run server
    openMode: tab-after

vscode:
  extensions:
    - formulahendry.auto-close-tag
    - coenraads.bracket-pair-colorizer
    - pkief.material-icon-theme
    - eamodio.gitlens
    - usernamehw.errorlens
    - >-
      https://marketplace.visualstudio.com/_apis/public/gallery/publishers/eg2/vsextensions/tslint/1.0.47/vspackage

ports:
  - port: 3000
    onOpen: open-browser
    visibility: public
  - port: 4000
    onOpen: ignore
    visibility: public

[faisal-m16]

Update: After removing env from task Run Client it worked fine. But I am still confused why it was not running with env

[jmcelreavey]

is 'env' a useable option? Have you tried the command: gp env DANGEROUSLY_DISABLE_HOST_CHECK=true

[faisal-m16]

https://www.gitpod.io/docs/references/gitpod-yml#tasksnenv env in tasks i defined here. I followed documentation.

I did other workaround in command: DANGEROUSLY_DISABLE_HOST_CHECK: true yarn start.

[csweichel]

/assign

[csweichel]

@jmcelreavey I'm afraid I cannot re-produce the issue. The repository you linked behaves as intended: the init task gets run during the prebuild, and is not re-executed when the workspace starts.

Note: we modify the terminal history to make it look like the task just ran. You can tell that the command ran as part of the prebuild because the log output appears before

🤙 This task ran as a workspace prebuild
🎉 Well done on saving 2 minutes

To make sure this behaviour doesn't break in the future (and as one more step to verify the correct behaviour), I've written a bunch of unit tests: #4903

[csweichel]

@faisal-m16 Unfortunately prebuilds don't give a whole lot of feedback when the .gitpod.yml has validation errors, which is what I suspect is the case here. We've recently added some functionality that provides feedback regarding the .gitpod.yml when opening the workspace. Please check if you see any validation errors when opening the workspace regularly.