Here is my mix:
mix.styles(paths.styles, './', 'public/css/app.css')
.scripts(paths.vendors,'./','public/js/vendor.js')
.scriptsIn(paths.app,'./public/js/app.js')
.version(['css/app.css','js/vendor.js','js/app.js']);
My expected result in build directory would be these below files with revision:
app.css
vendor.js
app.js
But after I ran gulp, I got only app.css and app.js.
Is there something wrong with my mix?
Related
I'm having trouble when I try to use the dir attribute of a step in my workflow. I have a directory like the following:
myproject/
folder/
subfolder/
And this is how my workflow looks like:
steps:
- uses: docker://alpine:3.12
dir: folder/subfolder
args: [pwd]
The above is stored in a wf.yml file, and I run it by doing:
cd myproject/
popper run -f wf.yml
But I'm getting the error:
ERROR: Schema validation failed:
- Key 'dir' was not defined. Path: '/steps/1'.
I am using Popper 2.6.0, and Docker 19.03.8
The dir feature in Popper is available in version 2.7.0+, so you will need to update to a newer version. In addition, as specified in the documentation, the path given to the dir attribute of a step has to be an absolute path. In the given example, since the folder being referenced is within the myproject/ folder, which is the one getting bind-mounted to /workspace inside the container, the workflow would look like:
steps:
- uses: docker://alpine:3.12
dir: /workspace/folder/subfolder
args: [pwd]
and the above should print /workspace/folder/subfolder.
I'm trying to set up a Jenkins build project with ReadyRoll. Mostly it is working but I'm getting warnings that concern me:
MSBUILD : OctoPack warning OCTNOENT: The source file 'c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\bin\Release\' does not exist, so it will not be included in the package [c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\CoreServices.sqlproj]
MSBUILD : OctoPack warning OCTNOENT: The source file 'c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\obj\Release\CoreServices_Package.sql' does not exist, so it will not be included in the package [c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\CoreServices.sqlproj]
I have searched for information on this error and have found nothing helpful. When I check the build server after the build is completed, the folder and file it says do not exist do, indeed, exist. That implies to me there is some sort of order of operation error going on here but I don't know where or how that would be occurring.
Here is the section of the log where the warnings are generated:
OctoPack:
Using package version: 8.6.26
OctoPack: OctoPack version: 3.6.1.0
OctoPack: Written files: 10
OctoPack: Copy file: c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\obj\Release\CoreServices.nuspec
OctoPack: Packaging a console or Window Service application (no Web.config detected)
OctoPack: Add binary files
OctoPack: Added file: CoreServices_Package.sql
OctoPack: Added file: CoreServices_DeployPackage.ps1
OctoPack: Added file: CoreServices_Snapshot.nupkg.bin
MSBUILD : OctoPack warning OCTNOENT: The source file 'c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\bin\Release\' does not exist, so it will not be included in the package [c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\CoreServices.sqlproj]
OctoPack: Added file: Deploy.ps1
OctoPack: Added file: DeployFailed.ps1
MSBUILD : OctoPack warning OCTNOENT: The source file 'c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\obj\Release\CoreServices_Package.sql' does not exist, so it will not be included in the package [c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\CoreServices.sqlproj]
OctoPack: Added file: CoreServices.dll
OctoPack: Added file: CoreServices.pdb
OctoPack: NuGet Version: 3.5.0.38733 (Custom build for OctoPack. See http://g.octopushq.com/VersioningInOctopusDeploy)
OctoPack: Attempting to build package from 'CoreServices.nuspec'.
OctoPack: Successfully created package 'c:\scm01-jenkins\workspace\DatabaseDeploys\DatabaseDeploys\CoreServices\obj\octopacked\IC_CoreServices.Database.8.6.26.nupkg'.
And here are the MSBuild parameters:
/t:Clean,Build /p:Version=8.6.26.0;Configuration=Release /p:GenerateSqlPackage=True /p:ShadowServer=[shadowdatabasename] /p:RunOctoPack=true /p:OctoPackPackageVersion=8.6.26 /p:OctoPackPublishPackageToHttp=http://[OctopusDeployServer]/nuget/packages /p:OctoPackPublishApiKey=[key]
Any ideas how to fix this?
Thank you.
Unfortunately this is a known issue with ReadyRoll's integration with OctoPack, however the warnings are extraneous and can be safely ignored.
To suppress the warnings, add the following to your MSBuild parameters:
/nowarn:OCTNOENT
I'll update this answer once the issue is resolved (1003).
A fix for this was released as part of ReadyRoll 1.16.18100; the OctoPack warnings should no longer be displayed during build.
How can I fix it or where do I fix it?
It should point to:
C:\jboss\jboss-5.1.0.GA\server\default\lib
Console log
C:\PSC Updated\src>ant build-ejb
Buildfile: C:\PSC Updated\src\build.xml
clean:
build-core:
[mkdir] Created dir: C:\PSC Updated\src\build\classes
[javac] Compiling 159 source files to C:\PSC Updated\src\build\classes
BUILD FAILED
C:\PSC Updated\src\build.xml:110: C:\home\apps\jboss-5.1.0.GA\server\default\lib does not exist.
Worked: When I pointed to my {jboss.home}\server\default\lib
Try double slash for windows path on ant files.
C:\\jboss\\jboss-5.1.0.GA\\server\\default\\lib
Could you post your build.xml for more clarification.
How can i generate an javascript test coverage using jstestdriver?
I am able to run the javascript test using jstestdriver. I want to generate a coverage report to check how much percentage of javascript files i have tested.
I have read through this website http://code.google.com/p/js-test-driver/wiki/CodeCoverage and followed the instructions provided. However, i still can not get a coverage report.
My folder struture right now is and the relevant files i have imported for coverage report:
-trunk
-app
-test
-lib
-jstestdriver
-javascipt (includes coverage.js, CoverageTest.js, Instrumentable.js, plugin.js)
-plugins (includes coverage.jar)
-unit
-controllerSpecs.js
-config
-coverage.conf
-scripts
- test-server.sh
- test.sh
- web-server.js
In my coverage.conf, I have the following content:
server: http://localhost:9876
load:
- test/lib/jstestdriver/javascript/coverage.js
- test/lib/jstestdriver/javascript/CoverageTest.js
- test/unit/*.js
plugin:
- name: "coverage"
jar: "test/lib/jstestdriver/plugins/coverage.jar"
module: "com.google.jstestdriver.coverage.CoverageModule"
exclude:
Thank you in advance for your help=)
It didn't work as expected for me either, but now it does. I'm not sure why but I think all I changed was the whitespace in the config file:
plugin:
- name: "coverage"
jar: "coverage-1.3.4.b.jar"
module: "com.google.jstestdriver.coverage.CoverageModule"
Note: the .dat file which was generated was empty the first time I ran this.
(I have the CodeCoverage jar in the same directory as the .conf file)
Part of my build process is to create a tar file of an input directory, located at src/bundle/bundle. In src/bundle/SConscript:
Import('*')
bundleDir = Dir("bundle")
jsontar = Command("bundle.tar", bundleDir,
"/home/dbender/bin/mkvgconf $SOURCE $TARGET")
in my SConstruct:
SConscript(Split('src/bundle/SConscript'),
exports='bin_env lib_env', build_dir='tmp/bundle')
When attempting to build:
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
/home/dbender/bin/mkvgconf tmp/bundle/bundle tmp/bundle/bundle.tar
Input directory tmp/bundle/bundle not found!
scons: *** [tmp/bundle/bundle.tar] Error 1
scons: building terminated because of errors.
Clearly scons is not copying the src/bundle/bundle to tmp/bundle/bundle, but I am stumped as to why.
Footnotes:
Using absolute pathname for mkvgconf is bad practice but just intermediate until I have this problem solved.
SCons doesn't know anything about the contents of your input src/bundle/bundle - only the program mkvgconf knows what it does with that directory.
One solution is to add an explicit dependency in the SConscript:
import os
Depends('bundle.tar', Glob(str(bundleDir) + os.path.sep + '*'))
That also means that when you update the contents of the bundle directory, the mkvgconf script will be rerun.
PS. you might want to change the build_dir argument name to variant_dir, as the former is deprecated in favor of the latter in recent SCons releases.