I have a Bamboo instance setup to do builds with the following config:
Bamboo version = 3.0.1
when running the build, i got the following error:
09-Mar-2011 08:57:50 Pulling from repository `/root/POC/PRS' to directory '/root/bamboo-ci/xml-data/build-dir/_hg-repositories-cache/d20373e808a2d0e95a604129054231a0da36ff99'
09-Mar-2011 08:57:50 pulling from /root/POC/PRAEFECTUS
09-Mar-2011 08:57:50 searching for changes
09-Mar-2011 08:57:50 no changes found
09-Mar-2011 08:57:50 Copying repository from cache directory to source directory...
09-Mar-2011 08:57:50 Creating empty repository in directory '/root/bamboo-ci/xml-data/build-dir/PRQA-PRQAKEY-JOB1'
09-Mar-2011 08:57:50 Pulling from repository `/root/bamboo-ci/xml-data/build-dir/_hg-repositories-cache/d20373e808a2d0e95a604129054231a0da36ff99' to directory '/root/bamboo-ci/xml-data/build-dir/PRQA-PRQAKEY-JOB1'
09-Mar-2011 08:57:51 pulling from /root/bamboo-ci/xml-data/build-dir/_hg-repositories-cache/d20373e808a2d0e95a604129054231a0da36ff99
09-Mar-2011 08:57:51 requesting all changes
09-Mar-2011 08:57:51 adding changesets
09-Mar-2011 08:57:51 adding manifests
09-Mar-2011 08:57:51 adding file changes
09-Mar-2011 08:57:51 added 1 changesets with 810 changes to 810 files
09-Mar-2011 08:57:51 (run 'hg update' to get a working copy)
09-Mar-2011 08:57:52 810 files updated, 0 files merged, 0 files removed, 0 files unresolved
09-Mar-2011 08:57:52 Updated source code to revision: cc40b2d9c09ea747529887dd8db9319f53c5db4e
09-Mar-2011 08:57:52 Executing build PRQA-PRQAKEY-JOB1-2
09-Mar-2011 08:57:52 Running pre-build action: Build Number Stamper
09-Mar-2011 08:57:52 Running pre-build action: Clover Grails PreBuild Action
09-Mar-2011 08:57:52 Running pre-build action: VCS Version Collector
09-Mar-2011 08:57:52 Running pre-build action: Repository Isolation Enabler Action
09-Mar-2011 08:57:52 Running pre-build action: Maven Settings Prebuild Action
09-Mar-2011 08:57:52 Building started with ScriptBuilder
09-Mar-2011 08:57:52
Starting to build 'PRAEFECTUS-QA - PRQA-PLAN - Default Job'
... running command line: /bin/sh Makefile
... in : /root/bamboo-ci/xml-data/build-dir/PRQA-PRQAKEY-JOB1
09-Mar-2011 08:57:52 Makefile: 10: PYTHON: not found
but if we look at the folder listed in the error, the Makefile is there
root#bambooserver:~/bamboo-ci/xml-data/build-dir/PRQA-PRQAKEY-JOB1# ls -l
total 104
-rw-r--r-- 1 root root 45 2011-03-09 08:57 AUTHORS
drwxr-xr-x 2 root root 4096 2011-03-09 08:57 bin
-rw-r--r-- 1 root root 138 2011-03-09 08:57 build-number.txt
-rw-r--r-- 1 root root 120 2011-03-09 08:57 CHANGES
-rwxr-xr-x 1 root root 9703 2011-03-09 08:57 ez_setup.py
drwxr-xr-x 2 root root 4096 2011-03-09 08:57 images
drwxr-xr-x 2 root root 4096 2011-03-09 08:57 init.d
drwxr-xr-x 5 root root 4096 2011-03-09 08:57 iped
drwxr-xr-x 2 root root 4096 2011-03-09 08:57 logrotate.d
-rw-r--r-- 1 root root 932 2011-03-09 08:57 Makefile
-rw-r--r-- 1 root root 175 2011-03-09 08:57 MANIFEST.in
drwxr-xr-x 2 root root 4096 2011-03-09 08:57 nbproject
-rw-r--r-- 1 root root 1109 2011-03-09 08:57 NEWS
drwxr-xr-x 5 root root 4096 2011-03-09 08:57 prs
drwxr-xr-x 3 root root 4096 2011-03-09 08:57 rpa
drwxr-xr-x 2 root root 4096 2011-03-09 08:57 sbin
drwxr-xr-x 4 root root 4096 2011-03-09 08:57 scripts
-rw-r--r-- 1 root root 81 2011-03-09 08:57 setup.cfg
-rwxr-xr-x 1 root root 2796 2011-03-09 08:57 setup.py
drwxr-xr-x 2 root root 4096 2011-03-09 08:57 src
drwxr-xr-x 7 root root 4096 2011-03-09 08:57 test
drwxr-xr-x 5 root root 4096 2011-03-09 08:57 tests
-rw-r--r-- 1 root root 501 2011-03-09 08:57 TODO
-rw-r--r-- 1 root root 6 2011-03-09 08:57 VERSION
root#bambooserver:~/bamboo-ci/xml-data/build-dir/PRQA-PRQAKEY-JOB1#
any tips on how to setup a Job in Bamboo ? i am using Mercurial and project is in Python.
As I can see you've used a ScriptBuilder which is dedicated to running a shell script while you probably need a builder that runs a command
make
What you need to do is:
go to Administration / Server Capabilities
in "Add Capability" select: Capability Type: Builder, Type: Command, Builder Label: Make, Path: enter the full path to your make utility (ie. /usr/bin/make)
now navigate to your plan configuration and change the builder to "Make"
After those changes your build should be working fine.
PS.
In case of future problems you should try reporting the problem on Atlassian's support site (http://support.atlassian.com)
Disclaimer: yes I work for Atlassian
Related
I got this message when editing my Go project in vscode:
The Go language server is currently not supported in a multi-root set-up with different GOPATHs.
My question is: what is a "multi-root-set-up"? I do not intend to make my project "multi-root". How to avoid this message, and let the language server analyze my code?
BTW, the directory layout of my project is:
drwxrwxr-x 5 xrfang xrfang 4096 1月 21 22:33 docs
drwxrwxr-x 2 xrfang xrfang 4096 1月 21 22:33 exp
-rw-rw-r-- 1 xrfang xrfang 789 2月 3 20:52 Makefile
drwxrwxr-x 3 xrfang xrfang 4096 2月 12 22:03 pkg
drwxrwxr-x 7 xrfang xrfang 4096 1月 31 11:56 resources
drwxrwxr-x 8 xrfang xrfang 4096 2月 12 21:27 src
-rw-rw-r-- 1 xrfang xrfang 304 1月 21 22:33 TODO
-rwxrwxr-x 1 xrfang xrfang 395 1月 21 22:33 upgrade.sh
drwxrwxr-x 2 xrfang xrfang 4096 2月 12 21:28 utils
The go.mod file is in src directory. And pkg is generated by the compiler, which is quite strange, because most of my other Go project does not generate pkg in the repository folder.
If you are using modules (go.mod), try to open vscode from the directory where go.mod exists.
If you are using GOPATH with the multiple paths and your intention is to work in the GOPATH mode, that's not supported as Ian said.
I hope https://github.com/golang/vscode-go#setting-up-your-workspace provides more info.
Also, make sure to have "go.inferGopath" setting disabled. I suspect the repository has been structured to work with the GOPATH mode and append the workspace root to the GOPATH. It's possible that vscode Go plugin + gopls does not like it. :-(
The error message is referring to your GOPATH environment variable. GOPATH permits multiple paths separate by a colon, but gopls does not support that.
I start off by deleting Gradle's build cache
$ rm -rf $GRADLE_HOME/caches/build-cache-*
I manually confirm this directory is gone. I also clean to ensure nothing from incremental build will interfere
$ ./gradlew clean
I then run a build w/ build-cache enabled:
$ ./gradlew --build-cache --scan app:assembleDebug
...
238 actionable tasks: 172 executed, 49 from cache, 17 up-to-date
Checking the generated report I see that some tasks are still marked as FROM-CACHE. How is this happening?
FWIW I'm using Gradle 5.6.3. I also don't use a remote build cache.
UPDATE: after clearing build cache, here's what's left in the cache dir:
$ pwd
/Users/jasonatwood/.gradle/caches
$ ls -al
total 24
drwx------ 11 jasonatwood staff 352 Dec 13 18:11 .
drwxr-xr-x 9 jasonatwood staff 288 Oct 15 17:24 ..
drwxr-xr-x 14 jasonatwood staff 448 Oct 29 16:07 5.4.1
drwxr-xr-x 15 jasonatwood staff 480 Nov 26 18:25 5.6.3
drwxr-xr-x 35 jasonatwood staff 1120 Dec 11 14:14 jars-3
drwxr-xr-x 5 jasonatwood staff 160 Oct 15 17:44 journal-1
drwxr-xr-x 7 jasonatwood staff 224 Oct 15 17:50 modules-2
drwxr-xr-x 5 jasonatwood staff 160 Oct 15 17:50 transforms-2
-rw-r--r-- 1 jasonatwood staff 39 Oct 15 17:27 transforms-2.lock
-rw------- 1 jasonatwood staff 28 Oct 22 16:34 user-id.txt
-rw-r--r-- 1 jasonatwood staff 17 Dec 13 18:00 user-id.txt.lock
If I understand correctly, I don't need to delete any of these.
The local task cache in the .gradle directory within the root project might interfere.
In order to disable the local/global caching altogether, use gradle.properties:
org.gradle.caching=false
If you remove the local build cache and don't use a remove cache, Gradle should indeed not be able to fetch anything cached on the next build. However, I don't think you actually removed anything.
The GRADLE_HOME environment variable, if you have it, should points to an unpacked local Gradle distribution. It could be something like /Users/jasonatwood/gradle-6.0-all. It would be wrong to set it to a path that is not a Gradle distribution.
The Gradle build cache resides in /Users/jasonatwood/.gradle/caches/build-cache-1.
When you try to remove it with $ rm -rf $GRADLE_HOME/caches/build-cache-*, you are using GRADLE_HOME as if it is pointing to the root of your home folder (/Users/jasonatwood), which it most likely isn't.
So instead, use this for removing it: $ rm -rf ~/.gradle/caches/build-cache-*
Or, at the very least, verify that the cache folder has indeed been removed.
If I run a --scan and look at the FROM-CACHE tasks in the generated HTML report.
I then look at the build cache keys for those FROM-CACHE tasks. I then go find those keys on my local machine. I see they are generated at the same time as the rest of the build. So I'm guessing that Gradle is using build cache within a build and not just across builds.
Sometimes there is a need to invalidate cache every time you restart the IDEA. This may be due to shared indexes reuse. What I did Settings --> Tools --> Shared Indexes -> Download Automatically and it resolved all the pain.
Earlier the setting was Don't download use Local.
In my laravel 5.7 / Bootstrap 4.1 app
I installed font-awesome package with command
npm install font-awesome --save
and in my package.json I have :
"dependencies": {
...
"font-awesome": "^4.7.0",
...
}
In webpack.mix.js there is line :
mix.copy('node_modules/font-awesome/fonts', 'public/fonts');
In fonts directory I see
nick#nick:project/public/fonts$ ls -la
total 1080
drwxrwxrwx 1 root root 4096 лис 9 14:32 .
drwxrwxrwx 1 root root 4096 лис 6 06:04 ..
-rwxrwxrwx 1 root root 134808 лис 9 14:32 FontAwesome.otf
-rwxrwxrwx 1 root root 165742 лис 9 14:32 fontawesome-webfont.eot
-rwxrwxrwx 1 root root 444379 лис 9 14:32 fontawesome-webfont.svg
-rwxrwxrwx 1 root root 165548 лис 9 14:32 fontawesome-webfont.ttf
-rwxrwxrwx 1 root root 98024 лис 9 14:32 fontawesome-webfont.woff
-rwxrwxrwx 1 root root 77160 лис 9 14:32 fontawesome-webfont.woff2
drwxrwxrwx 1 root root 4096 лис 7 10:16 roboto
drwxrwxrwx 1 root root 0 лип 22 08:07 vendor
The problem is when I try to use these icons, not all of them are rendered.
Say icons fa fa-alicorn or fa fa-air-freshener are empty.
I select icon from this https://fontawesome.com/icons?d=gallery&q=freshener selector.
You can check it by http://votes.nilov-sergey-demo-apps.tk/admin/dashboard url, under "Icons Samples" block there some some icons
which are visible, but some not.
Why? Are these different version of icons in my app?
Thanks!
The icons that are not displaying are not available in your fontawesome version. You are using fontawesome v4, the missing icons are only available in fontawesome v5.
Here you can find all icons available for v4:
Here you can find the install guide for v5.
I have IntelliJ CE and I just imported a Go project that I cloned from GitHub. On my Mac, I have some folder organization where I group projects that I work on based on the technologies. For example., in my Projects folder on my Mac, I have the following sub folders:
- go-projects
- scala-projects
- rust-projects
- ruby-projects
So I obviously checked out the Go project in the go-projects folder which looks like this:
Joes-MacBook-Pro:go-projects joe$ ll
total 0
drwxr-xr-x 3 joe staff 102B Oct 28 07:51 bin/
drwxr-xr-x 19 joe staff 646B Oct 24 06:48 golang-restful-starter-kit/
drwxr-xr-x 3 joe staff 102B Oct 28 07:51 pkg/
drwxr-xr-x 3 joe staff 102B Oct 27 10:23 src/
And if I get into the src folder, it looks like this:
Joes-MacBook-Pro:go-projects joe$ cd src
total 0
drwxr-xr-x 6 joe staff 204B Nov 7 19:14 github.com/
Joes-MacBook-Pro:src joe$ cd github.com/
total 0
drwxr-xr-x 3 joe staff 102B Oct 28 08:20 btcsuite/
drwxr-xr-x 16 joe staff 544B Nov 7 19:16 eth-client/
drwxr-xr-x 3 joe staff 102B Oct 27 10:24 ethereum/
drwxr-xr-x 3 joe staff 102B Oct 28 07:51 tools/
Joes-MacBook-Pro:github.com joe$
Here is my Go related environment settings:
# For Go projects, we set the GOPATH
export GOROOT="/usr/local/go"
export GOPATH="/Users/joe/Projects/Private/go-projects"
export GODEPS="/Users/joe/Projects/Private/go-projects/bin/godep"
Now I import one of the Go project into IntelliJ and I get to see the following error saying that it is not able to resolve a directory as it can be seen in the screenshot below!
How can I get rid of this error? Any ideas?
I just realized that when I clone the project, I should not do a git clone but rather do:
go get -u github.com/golang/lint/golint
Not sure why this is so, but after doing this my IntelliJ was able to resolve every file on my project!
For golang projects, it's good to have Goland installed ( also a product of JetBrains )Goland Download. Moreover for the above concern you can use:
go get *the_project_to_clone*
I stuck with this problem in my project, so, I tried it with an empty test project. Here is what I do.
Create a new Cocoa application project in Xcode.
Add a new command-line tool target to it.
Add this target to the dependencies of the cocoa app.
In cocoa app target build phases add Copy files build phase, Destination = Executables, add executable product to the list.
Now Run cocoa application. No problem, application launched. Navigate app bundle in Finder, Show package contents, executable here in Contents/MacOS. This is what I expect to be.
The problem occurs when I archive cocoa application, it fails with the following error:
(null): error: /Users/prudnikov/Library/Developer/Xcode/DerivedData/TestAppWithExecutable-hiysgipuqcktgoayxrgjfrtcxubl/Build/Intermediates/ArchiveIntermediates/TestAppWithExecutable/BuildProductsPath/Release/TestAppExecutable: No such file or directory
Here is a screenshot
Here is content of this directory
prudnikov#Vladimirs-iMac ~ $ ls -al /Users/prudnikov/Library/Developer/Xcode/DerivedData/TestAppWithExecutable-hiysgipuqcktgoayxrgjfrtcxubl/Build/Intermediates/ArchiveIntermediates/TestAppWithExecutable/BuildProductsPath/Release/
total 8
drwxr-xr-x 5 prudnikov staff 170B Apr 26 21:59 ./
drwxr-xr-x# 3 prudnikov staff 102B Apr 26 21:59 ../
drwxr-xr-x 3 prudnikov staff 102B Apr 26 21:59 TestAppExecutable.dSYM/
lrwxr-xr-x 1 prudnikov staff 239B Apr 26 21:59 TestAppWithExecutable.app# -> /Users/prudnikov/Library/Developer/Xcode/DerivedData/TestAppWithExecutable-hiysgipuqcktgoayxrgjfrtcxubl/Build/Intermediates/ArchiveIntermediates/TestAppWithExecutable/InstallationBuildProductsLocation/Applications/TestAppWithExecutable.app
drwxr-xr-x 3 prudnikov staff 102B Apr 26 21:59 TestAppWithExecutable.app.dSYM/
Archiving executable — no problems. All build settings are defaults.
I've also tried to change build configuration from Debug to Release for Run action of Cocoa application scheme. It runs successfully in this case as well.
This is very strange for me. Please advice how to do it?
UPDATE: It seems that I have problem with OS. People tried the same example and it worked. Then I trien to create a new account on my Mac and do the same there and it worked as well. What global configuration can cause this?
I don't think this is an Answer but it's too long for a comment.
Check the parent directories
gdunham: ~/Library/Developer/Xcode/DerivedData$ ls -laeG /Users/gdunham/Library/Developer/Xcode/DerivedData | grep -e " \\.$"
drwxr-xr-x 31 gdunham staff 1054 Apr 15 14:29 /Users/gdunham/Library/Developer/Xcode/DerivedData
drwxr-xr-x 13 gdunham staff 442 May 1 19:56 /Users/gdunham/Library/Developer/Xcode
drwxr-xr-x 4 gdunham staff 136 Mar 8 2012 /Users/gdunham/Library/Developer/
drwx------# 66 gdunham staff 2244 Apr 2 22:43 /Users/gdunham/Library
0: group:everyone deny delete
drwxr-xr-x+ 62 gdunham staff 2108 Apr 30 14:33 /Users/gdunham
0: group:everyone deny delete
drwxr-xr-x 7 root admin 238 Feb 20 14:16 /Users
drwxr-xr-x 34 root wheel 1224 Apr 20 09:26 /
Also look at your group membership
gdunham: ~/Library/Developer/Xcode/DerivedData$ groups
staff com.apple.access_screensharing com.apple.access_screensharing-disabled everyone _appstore localaccounts _appserverusr admin _appserveradm _lpadmin _lpoperator _developer com.apple.sharepoint.group.1