Require --locked when building runtime (#2813)

* Require --locked when building runtime

* Update locks

* Do it in a different way

* Accidentally reverted Cargo.lock

* pass on arguments in build.sh scripts

substrate/.gitlab-ci.yml

@@ -92,7 +92,7 @@ test-linux-stable:                 &test
     variables:
       - $DEPLOY_TAG
   script:
-    - ./scripts/build.sh
+    - ./scripts/build.sh --locked
     - time cargo test --all --release --verbose --locked
     - sccache -s
 
@@ -117,7 +117,7 @@ test-linux-stable-int:             &test
       - $DEPLOY_TAG
   before_script:
     - sccache -s
-    - ./scripts/build.sh
+    - ./scripts/build.sh --locked
   script:
     - time RUST_LOG=sync=trace,consensus=trace,client=trace,state-db=trace,db=trace,forks=trace,state_db=trace,storage_cache=trace cargo test -p node-cli --release --verbose --locked -- --ignored --test-threads=1
     - sccache -s
@@ -172,7 +172,7 @@ build-linux-release:
   tags:
     - linux-docker
   script:
-    - ./scripts/build.sh
+    - ./scripts/build.sh --locked
     - time cargo build --release --verbose
     - mkdir -p ./artifacts
     - mv ./target/release/substrate ./artifacts/.
@@ -204,7 +204,7 @@ build-rust-doc-release:
   tags:
     - linux-docker
   script:
-    - ./scripts/build.sh
+    - ./scripts/build.sh --locked
     - rm -f ./crate-docs/index.html # use it as an indicator if the job succeeds
     - time cargo +nightly doc --release --all --verbose
     - cp -R ./target/doc ./crate-docs